GithubHelp home page GithubHelp logo

Comments (6)

GoogleCodeExporter avatar GoogleCodeExporter commented on July 24, 2024
Ignore the template comments at the bottom (What version... Please provide...)

Original comment by [email protected] on 31 Jan 2011 at 10:58

from protostuff-googlecode-exported.

GoogleCodeExporter avatar GoogleCodeExporter commented on July 24, 2024
So you're basically using custom templates.
Its not relative because the <output> param is not a file but a string (id of 
an existing template or a path to a custom template)

If we were to use maven variables and a user generates with an existing 
template (java_bean) ... wouldn't it fail because src/main/resources/java_bean 
does not exist?

Try:
<output>${project.basedir}/path/to/your/custom/output.java.stg</output>

I don't see anything wrong with that and expect that work.  Don't you agree? :-)

Original comment by [email protected] on 31 Jan 2011 at 11:55

from protostuff-googlecode-exported.

GoogleCodeExporter avatar GoogleCodeExporter commented on July 24, 2024
no I am not using my own template for this.  Why did you think I was.  
Basically protostuff does not work in the same way protobuf does for files that 
are in subdirectories.  The only way I could make the files compatible with 
both was to have all of the files in the same directory, because protostuff 
doesn't interperate the PATH reference the same waay as protobuf.

So I dont think its working as I expected..  Dont you agree?  :-)

Original comment by [email protected] on 7 Feb 2011 at 11:11

from protostuff-googlecode-exported.

GoogleCodeExporter avatar GoogleCodeExporter commented on July 24, 2024
You've been busy aye.
Can you post an example set of protos that would work for protobuf and fail on 
protostuff? (would be faster to fix the bug)

Original comment by [email protected] on 7 Feb 2011 at 11:29

  • Changed state: Accepted

from protostuff-googlecode-exported.

GoogleCodeExporter avatar GoogleCodeExporter commented on July 24, 2024
Fixed @ rev 1249.
Brett, the output is now dependent on the project's baseDir when using custom 
stg templates.

Original comment by [email protected] on 9 Feb 2011 at 11:35

  • Changed state: Fixed

from protostuff-googlecode-exported.

GoogleCodeExporter avatar GoogleCodeExporter commented on July 24, 2024
great, will check it out, we were using ${project.basedir} in our configs as a 
workaround. 

thanks.

Original comment by [email protected] on 7 Mar 2011 at 4:54

from protostuff-googlecode-exported.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.