date:20101209

Re: Create complicated client jar release target(s)

2010-12-09 Thread Antonio Petrelli

2010/12/9 fhomasp thomas.peet...@realdolmen.com:
 You're talking about Tiles and accessing the parent directory.  Could you
 explain a bit further?

I have a better idea, here is the source:
http://svn.apache.org/repos/asf/tiles/framework/trunk/assembly/

 And the idea of an extra distribution module, that's not the way to go
 then?

I guess that *one* assembly module is enough. In Tiles, within that
single module, we build source, library, documentation assemblies from
one single module.

Antonio

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: avoiding overwriting newer file when using maven resources plugin copy-resources with filtering

2010-12-09 Thread Stephen Connolly

Sounds like you might be better served by writing your own plugin to do the
filtering, that way you can take the timestamps into consideration.

Also I hope you are putting the filtered java source into a sub-folder of
 ${basedir}/target

-Stephen

On 8 December 2010 22:49, Marshall Schor m...@schor.com wrote:



 On 12/8/2010 4:40 PM, Anders Hammar wrote:
  I guess the dependency plugin can't really tell, as the filtering takes a
  value outside of the source file which could have changed since the last
  time the file was filtered.
  The price you pay for filtering I guess?

 I was wondering (since I know the source of the filtered values) if there
 was
 a Maven-way of telling it this information?

 Something like being able to declare: file xyz depends on files abc and
 def, so
 if abc and def are both older than xyz, don't bother updating xyz.

 -Marshall Schor
  /Anders
 
  On Wed, Dec 8, 2010 at 18:02, Marshall Schor m...@schor.com wrote:
 
  The Maven resources plugin has a goal copy-resources which has a
  configuration
  parameter overwrite.  The default is false - meaning not to
 overwrite a
  target file if not needed (if the target has  a later date than the
  source).
 
  This setting is ignored, however, if the file is being filtered.
 
  I'm using this to inject version info from the POM into a Java source
 file.
   So
  everytime this module is built, it always updates this file even though
  nothing
  (usually) has changed.
 
  Is there a better Maven way to do this?
 
  -Marshall
 
  -
  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org
 
 

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org

Re: Create complicated client jar release target(s)

2010-12-09 Thread fhomasp


One for each artifact that needs to be released is ok, that wasn't my
question.

I now also have a distributionmodule that takes info from the release
modules in order to group the libraries and to create one release bundle, as
it is explained in the link you don't like much :-)

I'll take a look at this



Antonio Petrelli wrote:
 
 2010/12/9 fhomasp thomas.peet...@realdolmen.com:
 You're talking about Tiles and accessing the parent directory.  Could you
 explain a bit further?
 
 I have a better idea, here is the source:
 http://svn.apache.org/repos/asf/tiles/framework/trunk/assembly/
 
 And the idea of an extra distribution module, that's not the way to go
 then?
 
 I guess that *one* assembly module is enough. In Tiles, within that
 single module, we build source, library, documentation assemblies from
 one single module.
 
 Antonio
 
 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org
 
 
 

-- 
View this message in context: 
http://maven.40175.n5.nabble.com/Create-complicated-client-jar-release-target-s-tp3295582p3298637.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Using annotationProcessor in maven-compiler-plugin

2010-12-09 Thread Anders Hammar

I assume you tried the default value for generatedSourcesDirectory?
Haven't used annotation processors myself, my Maven experience just suggests
going with the defaults as much as possible. But if even the defaults don't
work, something is clearly wrong. Either in the plugin or in your config.
:-)

There is an integration-test regarding this for the maven-compiler-plugin.
Have look at that to see how that differs from your setup. Possible also
test with Maven 2.2.1 to see if Maven 3 is the problem.

/Anders

On Thu, Dec 9, 2010 at 05:35, lilyevsky leonidilyev...@yahoo.com wrote:

I am trying to learn how to use annotationProcessor feature with
maven-compiler-plugin 2.3.2 under maven 3.
My configuration is below.
The processor indeed works and it generates the files.
My problem is that the compiler does not see those files during compile
phase. What am I doing wrong?
I tried to put my generated-sources in different places, under target,
directly under the project folder.
I tried to use generated-sources/src/main/java structure. Nothing works.

build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.3.2/version
configuration
source1.6/source
target1.6/target

generatedSourcesDirectorygenerated-sources/src/main/java/generatedSourcesDirectory
annotationProcessors

annotationProcessorcom.newamsterdam.framework.flexrecord.FlexRecordProcessor/annotationProcessor
/annotationProcessors
/configuration
/plugin
/plugins
/build
--
View this message in context:
http://maven.40175.n5.nabble.com/Using-annotationProcessor-in-maven-compiler-plugin-tp3298435p3298435.html
Sent from the Maven - Users mailing list archive at Nabble.com.

42 matches

Mail list logo