Maven training and talks in Hong Kong at OSSummit Asia, 26-30 Nov 2007
The first OSSummit Asia is just around the corner, being held in Hong Kong, from 26-30 November. You can register for the conference and trainings now, or find out more information at http://www.ossummit.com/ Maven is again well represented with the following training and presentations: * Brett Porter and Maria Odea Ching: A Development Ecosystem with Apache Maven, Continuum and Archiva (includes OSSummit certification) http://www.ossummit.com/2007/program/talk/24 * Brett Porter: Apache Maven Best Practices http://www.ossummit.com/2007/program/talk/57 * Brett Porter: Repositories Everywhere! Managing modules at Apache and Eclipse http://www.ossummit.com/2007/program/talk/79 * Carlos Sanchez: Maven, Eclipse and OSGi working together http://www.ossummit.com/2007/program/talk/55 We also hope to have a Birds-of-a-feather (BOF) session during the conference for those interested in all things Maven. Note: if you can't make it to Hong Kong, there's still time to register for ApacheCon US in Atlanta. See this previous message for details of the Maven sessions being held there: http://tinyurl.com/ 32pz3u Hope to see you there! Regards, Brett -- Brett Porter - [EMAIL PROTECTED] Blog: http://www.devzuz.org/blogs/bporter/
Continuum training and talks in Hong Kong at OSSummit Asia, 26-30 Nov 2007
(posting here for the benefit of those not on the Maven lists) The first OSSummit Asia is just around the corner, being held in Hong Kong, from 26-30 November. You can register for the conference and trainings now, or find out more information at http://www.ossummit.com/ Continuum is again well represented with the following training and presentations: * Brett Porter and Maria Odea Ching: A Development Ecosystem with Apache Maven, Continuum and Archiva (includes OSSummit certification) http://www.ossummit.com/2007/program/talk/24 * Brett Porter: Apache Maven Best Practices http://www.ossummit.com/2007/program/talk/57 * Brett Porter: Repositories Everywhere! Managing modules at Apache and Eclipse http://www.ossummit.com/2007/program/talk/79 * Carlos Sanchez: Maven, Eclipse and OSGi working together http://www.ossummit.com/2007/program/talk/55 We also hope to have a Birds-of-a-feather (BOF) session during the conference for those interested in all things Maven. Note: if you can't make it to Hong Kong, there's still time to register for ApacheCon US in Atlanta. See this previous message for details of the Maven sessions being held there: http://tinyurl.com/ 32pz3u Hope to see you there! Regards, Brett -- Brett Porter - [EMAIL PROTECTED] Blog: http://www.devzuz.org/blogs/bporter/
Archiva training and talks in Hong Kong at OSSummit Asia, 26-30 Nov 2007
(posting here for the benefit of those not on the Maven lists) The first OSSummit Asia is just around the corner, being held in Hong Kong, from 26-30 November. You can register for the conference and trainings now, or find out more information at http://www.ossummit.com/ Archiva is again well represented with the following training and presentations: * Brett Porter and Maria Odea Ching: A Development Ecosystem with Apache Maven, Continuum and Archiva (includes OSSummit certification) http://www.ossummit.com/2007/program/talk/24 * Brett Porter: Apache Maven Best Practices http://www.ossummit.com/2007/program/talk/57 * Brett Porter: Repositories Everywhere! Managing modules at Apache and Eclipse http://www.ossummit.com/2007/program/talk/79 * Carlos Sanchez: Maven, Eclipse and OSGi working together http://www.ossummit.com/2007/program/talk/55 We also hope to have a Birds-of-a-feather (BOF) session during the conference for those interested in all things Maven. Note: if you can't make it to Hong Kong, there's still time to register for ApacheCon US in Atlanta. See this previous message for details of the Maven sessions being held there: http://tinyurl.com/ 32pz3u Hope to see you there! Regards, Brett -- Brett Porter - [EMAIL PROTECTED] Blog: http://www.devzuz.org/blogs/bporter/
Re: Ant tasks 2.0.7 with snapshot dependencies
Hi Mark, There have been some issues fixed with SNAPSHOT handling during last weeks: can you check if you still have a problem with latest tasks snapshot? You can find it in http://maven.zones.apache.org/continuum/workingCopy.action?projectId=524&userDirectory=target Then, if the problem is still present, we'll have to work on a testcase to reproduce it. Regards, Hervé Le lundi 15 octobre 2007, Mark Hobson a écrit : > Hi there, > > I'm upgrading to the latest maven-ant-tasks 2.0.7 from 2.0.4 and am > having problems downloading snapshot dependencies. My build.xml is > something like: > > http://xxx/";> > > > > http://yyy/";> > > > > >version="myVersion-SNAPSHOT"/> > > > > > But it's failing downloading the snapshot artifact since it's trying > to download a URL ending with "-SNAPSHOT", and not the > "-mmdd-hhmmss-n" version. So it appears to be assuming a remote > repo with uniqueVersion=true when this is not the case. I've had a > quick browse of the code and it appears uniqueVersion=false for > build.xml declared repos, so not sure what's happening here? > > Is this a known issue? > > Cheers, > > Mark > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
classpath, tests, resources
Hi,
I am experiencing a problem with testing and resources. Basically, it
seems the production and not the test resources are used when running
tests.
I have two log4j.properties files, one defines appender as file
appender in src/main/resources:
log4j.appender.dest1=org.apache.log4j.RollingFileAppender
log4j.appender.dest1.File=${catalina.home}/logs/provisioning.log
the test one in src/test/resources defines console appender:
log4j.appender.dest1=org.apache.log4j.ConsoleAppender
When I run mvn clean test, I end up with an exception:
java.io.FileNotFoundException: /logs/provisioning.log (No such file or
directory)
at java.io.FileOutputStream.openAppend(Native Method)
at java.io.FileOutputStream.(FileOutputStream.java:177)
at java.io.FileOutputStream.(FileOutputStream.java:102)
at org.apache.log4j.FileAppender.setFile(FileAppender.java:289)
at
org.apache.log4j.RollingFileAppender.setFile(RollingFileAppender.java:167)
at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:163)
at
org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:256)
at
org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:132)
at
org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:96)
at
org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:654)
at
org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:612)
at
org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConfigurator.java:509)
at
org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:415)
at
org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:441)
at
org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:470)
at org.apache.log4j.LogManager.(LogManager.java:122)
at org.apache.log4j.Logger.getLogger(Logger.java:104)
at
com.mycompany.project.I18NProviderInvocationHandler.(I18NProviderInvocationHandler.java:80)
however, when I delete the production log4j.properties file, the tests pass.
This is what System.out.println(System.getProperty("java.class.path")); returns:
/home/me/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-7/plexus-archiver-1.0-alpha-7.jar
/home/me/.m2/repository/org/codehaus/plexus/plexus-utils/1.4.5/plexus-utils-1.4.5.jar
/home/me/.m2/repository/org/apache/maven/surefire/surefire-api/2.4-jboss-1-SNAPSHOT/surefire-api-2.4-jboss-1-SNAPSHOT.jar
/home/me/.m2/repository/org/codehaus/plexus/plexus-container-default/1.0-alpha-8/plexus-container-default-1.0-alpha-8.jar
/home/me/.m2/repository/classworlds/classworlds/1.1-alpha-2/classworlds-1.1-alpha-2.jar
/home/me/.m2/repository/commons-lang/commons-lang/2.1/commons-lang-2.1.jar
/home/me/.m2/repository/org/apache/maven/surefire/surefire-booter/2.4-jboss-1-SNAPSHOT/surefire-booter-2.4-jboss-1-SNAPSHOT.jar
/home/me/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
However, when run from eclipse (the test fails the same way as when
run from command line), the classpath looks different:
/home/me/workspace.3.3/provisioning/src/main/resources/
/home/me/workspace.3.3/provisioning/src/test/resources/
/home/me/workspace.3.3/provisioning/target/classes/
/home/me/workspace.3.3/project/target/classes/
/home/me/.m2/repository/aopalliance/aopalliance/1.0/aopalliance-1.0.jar
/home/me/.m2/repository/avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar
/home/me/.m2/repository/com/mycompany/ipnutil/1.0.1/ipnutil-1.0.1.jar
/home/me/.m2/repository/com/swiftmq/jndi/6.1.0/jndi-6.1.0.jar
etc.
mvn help:effective-pom seems ok:
/home/me/workspace.3.3/provisioning/src/main/resources
/home/me/workspace.3.3/provisioning/src/test/resources
all is run on maven 2.0.7 and java 1.6.0_01.
Thanks for hints,
ondrej cernos
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: classpath, tests, resources
Hi Ondrej
looks like mvn is not only picking up the production log4j.properties file but
it's also probably not substituting ${catalina.home}
Check in your target/classes directory for log4j.properties and see if it's
substituted it.
Secondly, log4j uses the first log4j.properties it comes across, so it's not
going to see the second one in src/test/resources
There are many different ways of doing it - having just one log4j.properties in
src/main/resources and doing substitution using parameters from a default
profile for testing would be one method. You could change those by invoking a
production profile when you build the war for release.
Ondřej Černoš on 22/10/07 13:04, wrote:
I am experiencing a problem with testing and resources. Basically, it
seems the production and not the test resources are used when running
tests.
I have two log4j.properties files, one defines appender as file
appender in src/main/resources:
log4j.appender.dest1=org.apache.log4j.RollingFileAppender
log4j.appender.dest1.File=${catalina.home}/logs/provisioning.log
the test one in src/test/resources defines console appender:
log4j.appender.dest1=org.apache.log4j.ConsoleAppender
When I run mvn clean test, I end up with an exception:
java.io.FileNotFoundException: /logs/provisioning.log (No such file or
directory)
at java.io.FileOutputStream.openAppend(Native Method)
at java.io.FileOutputStream.(FileOutputStream.java:177)
at java.io.FileOutputStream.(FileOutputStream.java:102)
at org.apache.log4j.FileAppender.setFile(FileAppender.java:289)
at
org.apache.log4j.RollingFileAppender.setFile(RollingFileAppender.java:167)
at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:163)
at
org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:256)
at
org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:132)
at
org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:96)
at
org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:654)
at
org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:612)
at
org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConfigurator.java:509)
at
org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:415)
at
org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:441)
at
org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:470)
at org.apache.log4j.LogManager.(LogManager.java:122)
at org.apache.log4j.Logger.getLogger(Logger.java:104)
at
com.mycompany.project.I18NProviderInvocationHandler.(I18NProviderInvocationHandler.java:80)
however, when I delete the production log4j.properties file, the tests pass.
This is what System.out.println(System.getProperty("java.class.path")); returns:
/home/me/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-7/plexus-archiver-1.0-alpha-7.jar
/home/me/.m2/repository/org/codehaus/plexus/plexus-utils/1.4.5/plexus-utils-1.4.5.jar
/home/me/.m2/repository/org/apache/maven/surefire/surefire-api/2.4-jboss-1-SNAPSHOT/surefire-api-2.4-jboss-1-SNAPSHOT.jar
/home/me/.m2/repository/org/codehaus/plexus/plexus-container-default/1.0-alpha-8/plexus-container-default-1.0-alpha-8.jar
/home/me/.m2/repository/classworlds/classworlds/1.1-alpha-2/classworlds-1.1-alpha-2.jar
/home/me/.m2/repository/commons-lang/commons-lang/2.1/commons-lang-2.1.jar
/home/me/.m2/repository/org/apache/maven/surefire/surefire-booter/2.4-jboss-1-SNAPSHOT/surefire-booter-2.4-jboss-1-SNAPSHOT.jar
/home/me/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
However, when run from eclipse (the test fails the same way as when
run from command line), the classpath looks different:
/home/me/workspace.3.3/provisioning/src/main/resources/
/home/me/workspace.3.3/provisioning/src/test/resources/
/home/me/workspace.3.3/provisioning/target/classes/
/home/me/workspace.3.3/project/target/classes/
/home/me/.m2/repository/aopalliance/aopalliance/1.0/aopalliance-1.0.jar
/home/me/.m2/repository/avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar
/home/me/.m2/repository/com/mycompany/ipnutil/1.0.1/ipnutil-1.0.1.jar
/home/me/.m2/repository/com/swiftmq/jndi/6.1.0/jndi-6.1.0.jar
etc.
mvn help:effective-pom seems ok:
/home/me/workspace.3.3/provisioning/src/main/resources
/home/me/workspace.3.3/provisioning/src/test/resources
all is run on maven 2.0.7 and java 1.6.0_01.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: classpath, tests, resources
Hi Adam,
thanks for quick answer. The target/classes directory contains the
production log4j.properties file. I always thought maven uses the
target/test-classes directory as the classpath entry during the tests
- it contains the correct version of the log4j.properties file, but it
seems the target/classes directory is on the test classpath too, and
that it is even the first target directory mentioned on the classpath.
I was probably wrong. I'll try the profile tricks.
ondrej cernos
On 10/22/07, Adam Hardy <[EMAIL PROTECTED]> wrote:
> Hi Ondrej
>
> looks like mvn is not only picking up the production log4j.properties file
> but
> it's also probably not substituting ${catalina.home}
>
> Check in your target/classes directory for log4j.properties and see if it's
> substituted it.
>
> Secondly, log4j uses the first log4j.properties it comes across, so it's not
> going to see the second one in src/test/resources
>
> There are many different ways of doing it - having just one log4j.properties
> in
> src/main/resources and doing substitution using parameters from a default
> profile for testing would be one method. You could change those by invoking
> a
> production profile when you build the war for release.
>
> Ondřej Černoš on 22/10/07 13:04, wrote:
> > I am experiencing a problem with testing and resources. Basically, it
> > seems the production and not the test resources are used when running
> > tests.
> >
> > I have two log4j.properties files, one defines appender as file
> > appender in src/main/resources:
> >
> > log4j.appender.dest1=org.apache.log4j.RollingFileAppender
> > log4j.appender.dest1.File=${catalina.home}/logs/provisioning.log
> >
> > the test one in src/test/resources defines console appender:
> >
> > log4j.appender.dest1=org.apache.log4j.ConsoleAppender
> >
> > When I run mvn clean test, I end up with an exception:
> >
> > java.io.FileNotFoundException: /logs/provisioning.log (No such file or
> > directory)
> > at java.io.FileOutputStream.openAppend(Native Method)
> > at java.io.FileOutputStream.(FileOutputStream.java:177)
> > at java.io.FileOutputStream.(FileOutputStream.java:102)
> > at org.apache.log4j.FileAppender.setFile(FileAppender.java:289)
> > at
> org.apache.log4j.RollingFileAppender.setFile(RollingFileAppender.java:167)
> > at
> org.apache.log4j.FileAppender.activateOptions(FileAppender.java:163)
> > at
> org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:256)
> > at
> org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:132)
> > at
> org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:96)
> > at
> org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:654)
> > at
> org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:612)
> > at
> org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConfigurator.java:509)
> > at
> org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:415)
> > at
> org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:441)
> > at
> org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:470)
> > at org.apache.log4j.LogManager.(LogManager.java:122)
> > at org.apache.log4j.Logger.getLogger(Logger.java:104)
> > at
> com.mycompany.project.I18NProviderInvocationHandler.(I18NProviderInvocationHandler.java:80)
> >
> > however, when I delete the production log4j.properties file, the tests
> pass.
> >
> > This is what System.out.println(System.getProperty("java.class.path"));
> returns:
> >
> >
> /home/me/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-7/plexus-archiver-1.0-alpha-7.jar
> >
> /home/me/.m2/repository/org/codehaus/plexus/plexus-utils/1.4.5/plexus-utils-1.4.5.jar
> >
> /home/me/.m2/repository/org/apache/maven/surefire/surefire-api/2.4-jboss-1-SNAPSHOT/surefire-api-2.4-jboss-1-SNAPSHOT.jar
> >
> /home/me/.m2/repository/org/codehaus/plexus/plexus-container-default/1.0-alpha-8/plexus-container-default-1.0-alpha-8.jar
> >
> /home/me/.m2/repository/classworlds/classworlds/1.1-alpha-2/classworlds-1.1-alpha-2.jar
> > /home/me/.m2/repository/commons-lang/commons-lang/2.1/commons-lang-2.1.jar
> >
> /home/me/.m2/repository/org/apache/maven/surefire/surefire-booter/2.4-jboss-1-SNAPSHOT/surefire-booter-2.4-jboss-1-SNAPSHOT.jar
> > /home/me/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
> >
> > However, when run from eclipse (the test fails the same way as when
> > run from command line), the classpath looks different:
> >
> > /home/me/workspace.3.3/provisioning/src/main/resources/
> > /home/me/workspace.3.3/provisioning/src/test/resources/
> > /home/me/workspace.3.3/provisioning/target/classes/
> > /home/me/workspace.3.3/project/target/classes/
> > /home/me/.m2/repository/aopalliance/aopalliance/1.0/aopalliance-1.0.jar
> >
>
Re: classpath, tests, resources
You're right, I overlooked that, but your output didn't show the source paths at
all for mvn - just for eclipse.
Ondřej Černoš on 22/10/07 13:25, wrote:
thanks for quick answer. The target/classes directory contains the
production log4j.properties file. I always thought maven uses the
target/test-classes directory as the classpath entry during the tests
- it contains the correct version of the log4j.properties file, but it
seems the target/classes directory is on the test classpath too, and
that it is even the first target directory mentioned on the classpath.
I was probably wrong. I'll try the profile tricks.
ondrej cernos
On 10/22/07, Adam Hardy <[EMAIL PROTECTED]> wrote:
Hi Ondrej
looks like mvn is not only picking up the production log4j.properties file
but
it's also probably not substituting ${catalina.home}
Check in your target/classes directory for log4j.properties and see if it's
substituted it.
Secondly, log4j uses the first log4j.properties it comes across, so it's not
going to see the second one in src/test/resources
There are many different ways of doing it - having just one log4j.properties
in
src/main/resources and doing substitution using parameters from a default
profile for testing would be one method. You could change those by invoking
a
production profile when you build the war for release.
Ondřej Černoš on 22/10/07 13:04, wrote:
I am experiencing a problem with testing and resources. Basically, it
seems the production and not the test resources are used when running
tests.
I have two log4j.properties files, one defines appender as file
appender in src/main/resources:
log4j.appender.dest1=org.apache.log4j.RollingFileAppender
log4j.appender.dest1.File=${catalina.home}/logs/provisioning.log
the test one in src/test/resources defines console appender:
log4j.appender.dest1=org.apache.log4j.ConsoleAppender
When I run mvn clean test, I end up with an exception:
java.io.FileNotFoundException: /logs/provisioning.log (No such file or
directory)
at java.io.FileOutputStream.openAppend(Native Method)
at java.io.FileOutputStream.(FileOutputStream.java:177)
at java.io.FileOutputStream.(FileOutputStream.java:102)
at org.apache.log4j.FileAppender.setFile(FileAppender.java:289)
at
org.apache.log4j.RollingFileAppender.setFile(RollingFileAppender.java:167)
at
org.apache.log4j.FileAppender.activateOptions(FileAppender.java:163)
at
org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:256)
at
org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:132)
at
org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:96)
at
org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:654)
at
org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:612)
at
org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConfigurator.java:509)
at
org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:415)
at
org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:441)
at
org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:470)
at org.apache.log4j.LogManager.(LogManager.java:122)
at org.apache.log4j.Logger.getLogger(Logger.java:104)
at
com.mycompany.project.I18NProviderInvocationHandler.(I18NProviderInvocationHandler.java:80)
however, when I delete the production log4j.properties file, the tests
pass.
This is what System.out.println(System.getProperty("java.class.path"));
returns:
/home/me/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-7/plexus-archiver-1.0-alpha-7.jar
/home/me/.m2/repository/org/codehaus/plexus/plexus-utils/1.4.5/plexus-utils-1.4.5.jar
/home/me/.m2/repository/org/apache/maven/surefire/surefire-api/2.4-jboss-1-SNAPSHOT/surefire-api-2.4-jboss-1-SNAPSHOT.jar
/home/me/.m2/repository/org/codehaus/plexus/plexus-container-default/1.0-alpha-8/plexus-container-default-1.0-alpha-8.jar
/home/me/.m2/repository/classworlds/classworlds/1.1-alpha-2/classworlds-1.1-alpha-2.jar
/home/me/.m2/repository/commons-lang/commons-lang/2.1/commons-lang-2.1.jar
/home/me/.m2/repository/org/apache/maven/surefire/surefire-booter/2.4-jboss-1-SNAPSHOT/surefire-booter-2.4-jboss-1-SNAPSHOT.jar
/home/me/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
However, when run from eclipse (the test fails the same way as when
run from command line), the classpath looks different:
/home/me/workspace.3.3/provisioning/src/main/resources/
/home/me/workspace.3.3/provisioning/src/test/resources/
/home/me/workspace.3.3/provisioning/target/classes/
/home/me/workspace.3.3/project/target/classes/
/home/me/.m2/repository/aopalliance/aopalliance/1.0/aopalliance-1.0.jar
/home/me/.m2/repository/avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar
/home/me/.m2/repository/co
reading pom.version from a file
Hi,
What would be the right way to read the version number from a file?
We decided that not all users (who maybe don't know maven very well) should
check out the delicate pom file .
We have a file like version.properties containing
tavx.current.version=1.2.3a
and defined in the pom
4.0.0
com.abc.tat.tavx
tavx
adapter
jar
${tavx.current.version}
...
src/resources/version/version.properties
but that doesn't work.
Thanks for help
Markus
--
View this message in context:
http://www.nabble.com/reading-pom.version-from-a-file-tf4670564s177.html#a13342350
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
jsunit integration
Hello, I am working on integrating jsunit (http://www.jsunit.net) into maven. I would like to share some thoughts and request some advices avout the best way to do that integration. Right now, I have a sample (maven) project that executes jsunit tests from maven and generates reports. What I did is: - modify jsunit java server test cases to generate JUnit test results from jsunit test results: That way javascript unit tests results and error gets integrated seamlessly into surefire's reports - package the java server as an artifact - encapsulates all tests in a single JUnit tests cases that configures things and laucn jsunit's StandaloneTest class Some problems are: - test pages contains hardwired and absolute references to everything (ie. scripts and jsunti base directory) which is BAD ! - you need to install jsunit somewhere locally - you need to modify and track files by hand outside of the scope of the project - test server is started once for each test execution or event each JUnit test class execution which can be a performance bottleneck for large and/or deep projects What I want to do is: 1. package jsunit runner and support files as a jar or zip 2. create a plugin tbound to process-test-sources that would unpack the jsunit site in target/jsunit-runner 3. configure generically test server/runners to have target/jsunit-runner as their root site. This implies that javascript source files, test files and test pages be moved to this directory too... Ideally, I would rather serve everything from a servlet launched through jetty with the adequate maven plugin but this would require heavy changes to jsunit java server code. Or may be not... Comments and ideas are welcomed, regards, -- OQube < software engineering \ génie logiciel > Arnaud Bailly, Dr. \web> http://www.oqube.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Downloading dependency sources
Hi Everyone, Is there a way to tell maven to download source jars by default? I didn't see anything in the pom or settings model to do this. I know I can download sources using the eclipse plugin or the dependency plugin, but I would like to tell maven to always download source jars when building a project. Thanks! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jsunit integration
FYI I've started a javascript plugin project as part of maven Mojo. It allready support running jsunit tests : http://svn.codehaus.org/mojo/trunk/sandbox/javascript-maven-tools You can look at javascript-maven-plugin JsUnitMojo, that runs a customized TestCase with a shared jsUnit server to avoid the server-per-test issue you noticed. You will not be able to run the plugin as many dependencies are not (yet) available in central repo. You can look at the src/it projects on how to configure and use the plugin for jsunit tests. Could you give me an example of the test result generated from jsunit result ? This part of the plugin is far perfectible, and I would welcome contribution ;-) Nico. 2007/10/22, Insitu <[EMAIL PROTECTED]>: > > Hello, > I am working on integrating jsunit (http://www.jsunit.net) into > maven. I would like to share some thoughts and request some advices > avout the best way to do that integration. > > Right now, I have a sample (maven) project that executes jsunit tests > from maven and generates reports. What I did is: > - modify jsunit java server test cases to generate JUnit test results >from jsunit test results: That way javascript unit tests results >and error gets integrated seamlessly into surefire's reports > - package the java server as an artifact > - encapsulates all tests in a single JUnit tests cases that >configures things and laucn jsunit's StandaloneTest class > > Some problems are: > - test pages contains hardwired and absolute references to everything >(ie. scripts and jsunti base directory) which is BAD ! > - you need to install jsunit somewhere locally > - you need to modify and track files by hand outside of the scope of >the project > - test server is started once for each test execution or event each >JUnit test class execution which can be a performance bottleneck >for large and/or deep projects > > What I want to do is: > 1. package jsunit runner and support files as a jar or zip > 2. create a plugin tbound to process-test-sources that would unpack > the jsunit site in target/jsunit-runner > 3. configure generically test server/runners to have > target/jsunit-runner as their root site. This implies that > javascript source files, test files and test pages be moved to > this directory too... > > Ideally, I would rather serve everything from a servlet launched > through jetty with the adequate maven plugin but this would require > heavy changes to jsunit java server code. Or may be not... > > Comments and ideas are welcomed, > > regards, > -- > OQube < software engineering \ génie logiciel > > Arnaud Bailly, Dr. > \web> http://www.oqube.com > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Maven 2 bug @ throw new
We have two child modules where first one is a dependency of first one.
We are getting compilation error . cannot find symbol when compiling code
in second module which relates to AppException in first module.
The bug is that this line:
throw new AppException("cannot find PaperStruct for id: " +
getTransactionArea());
gives us error and is indicated as error in mevenIDE in netbeans.
where this line next to first one is not indicated as a Error.
new AppException();
You can use AppException everywhere but not in throw clause.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Maven 2 bug @ throw new
We have two child modules where first one is a dependency of first one.
We are getting compilation error . cannot find symbol when compiling code
in second module which relates to AppException in first module.
The bug is that this line:
throw new AppException("cannot find PaperStruct for id: " +
getTransactionArea());
gives us error and is indicated as error in mevenIDE in netbeans.
where this line next to first one is not indicated as a Error.
new AppException();
You can use AppException everywhere but not in throw clause.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: jsunit integration
The recurring issue seems to be getting JSUnit dependencies from Maven. Is there a dialog open with the JSUnit team about this? I've made an attempt but heard nothing: http://tech.groups.yahoo.com/group/jsunit/message/954 In my opinion, the ideal solution would be to get JSUnit building with a set of dependencies are are compatible with that's in Maven central (adding some more if necessary, like start.jar for jetty5x), and itself deploying artifact(s) of its own. I've myself started working on JSUnit's build.xml and to use Maven Antlib and created a pom to do just that (I can send it to anyone who's interested); I think the only thing it needs missing is start.jar. Here's relevant threads from the JSUnit list: http://tech.groups.yahoo.com/group/jsunit/message/988 I also think that Nico's approach of breaking jsunit-app into its own artifact to run inside Jetty, merged with a project's test cases and dependencies, is worth looking more at. Harlan On 10/22/07, nicolas de loof <[EMAIL PROTECTED]> wrote: > > FYI I've started a javascript plugin project as part of maven Mojo. It > allready support running jsunit tests : > > http://svn.codehaus.org/mojo/trunk/sandbox/javascript-maven-tools > > You can look at javascript-maven-plugin JsUnitMojo, that runs a customized > TestCase with a shared jsUnit server to avoid the server-per-test issue > you > noticed. > > You will not be able to run the plugin as many dependencies are not (yet) > available in central repo. > You can look at the src/it projects on how to configure and use the plugin > for jsunit tests. > > Could you give me an example of the test result generated from jsunit > result > ? This part of the plugin is far perfectible, and I would welcome > contribution ;-) > > Nico. > > > 2007/10/22, Insitu <[EMAIL PROTECTED]>: > > > > Hello, > > I am working on integrating jsunit ( http://www.jsunit.net) into > > maven. I would like to share some thoughts and request some advices > > avout the best way to do that integration. > > > > Right now, I have a sample (maven) project that executes jsunit tests > > from maven and generates reports. What I did is: > > - modify jsunit java server test cases to generate JUnit test results > >from jsunit test results: That way javascript unit tests results > >and error gets integrated seamlessly into surefire's reports > > - package the java server as an artifact > > - encapsulates all tests in a single JUnit tests cases that > >configures things and laucn jsunit's StandaloneTest class > > > > Some problems are: > > - test pages contains hardwired and absolute references to everything > >(ie. scripts and jsunti base directory) which is BAD ! > > - you need to install jsunit somewhere locally > > - you need to modify and track files by hand outside of the scope of > >the project > > - test server is started once for each test execution or event each > >JUnit test class execution which can be a performance bottleneck > >for large and/or deep projects > > > > What I want to do is: > > 1. package jsunit runner and support files as a jar or zip > > 2. create a plugin tbound to process-test-sources that would unpack > > the jsunit site in target/jsunit-runner > > 3. configure generically test server/runners to have > > target/jsunit-runner as their root site. This implies that > > javascript source files, test files and test pages be moved to > > this directory too... > > > > Ideally, I would rather serve everything from a servlet launched > > through jetty with the adequate maven plugin but this would require > > heavy changes to jsunit java server code. Or may be not... > > > > Comments and ideas are welcomed, > > > > regards, > > -- > > OQube < software engineering \ génie logiciel > > > Arnaud Bailly, Dr. > > \web> http://www.oqube.com > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > >
Re: jsunit integration
"nicolas de loof" <[EMAIL PROTECTED]> writes:
> FYI I've started a javascript plugin project as part of maven Mojo. It
> allready support running jsunit tests :
>
> http://svn.codehaus.org/mojo/trunk/sandbox/javascript-maven-tools
>
Ah ah, that's good. I was a bit lost with all those javascript plugins
laying around... I used maven-jstools as a base because I a mostly
interested irght now in jsdoc and jslint, not packing.
> You can look at javascript-maven-plugin JsUnitMojo, that runs a customized
> TestCase with a shared jsUnit server to avoid the server-per-test issue you
> noticed.
>
> You will not be able to run the plugin as many dependencies are not (yet)
> available in central repo.
Could'nt you make them available ? Or give directions on how to build
these dependencies ? I assume these are the static files for jsunit
runner. I could build them myself.
> You can look at the src/it projects on how to configure and use the plugin
> for jsunit tests.
>
> Could you give me an example of the test result generated from jsunit result
> ? This part of the plugin is far perfectible, and I would welcome
> contribution ;-)
>
I just wrote a mapper class that constructs a
TestResult object from the results generated by jsunit:
public class BrowseResultToJUnitResult {
private TestResult testResult;
public BrowseResultToJUnitResult(TestResult tr) {
this.testResult = tr;
}
/**
* Add all the testcases found in the given test result to
this junit
* TestResult.
*
* @param res
*a BrowserResult instance.
*/
public void addBrowserResult(BrowserResult res) {
for (final TestCaseResult tcr :
res.getTestCaseResults()) {
Test t = new Test() {
public void run(TestResult arg0) {
}
public int countTestCases() {
return 1;
}
public String toString() {
return tcr.getName();
}
};
testResult.startTest(t);
if (!tcr.wasSuccessful()) {
ResultType type = tcr.getResultType();
if (type == ResultType.ERROR) {
testResult.addError(t, new
Exception(tcr.getError()));
} else if (type == ResultType.FAILURE)
{
testResult.addFailure(t, new
AssertionFailedError(tcr
.getFailure()));
}
}
testResult.endTest(t);
}
}
}
and here are the tests:
public class MapAcceptorToTestResultTest extends TestCase {
public void testLoadResultFileAndCreateTestResult() throws
IOException {
String xml = "acceptor-sample.xml";
String value = xmlAsString(xml);
BrowserResultBuilder builder = new
BrowserResultBuilder(
new DummyBrowserSource("toto", 1));
BrowserResult res = builder.build(value);
TestResult tr = new TestResult();
BrowseResultToJUnitResult jres = new
BrowseResultToJUnitResult(tr);
jres.addBrowserResult(res);
assertEquals(8, tr.runCount());
assertEquals(0, tr.errorCount());
}
public void testLoadResultWithFailuresAndCreateTestResult()
throws IOException {
String xml = "acceptor-sample2.xml";
String value = xmlAsString(xml);
BrowserResultBuilder builder = new
BrowserResultBuilder(
new DummyBrowserSource("toto", 1));
BrowserResult res = builder.build(value);
TestResult tr = new TestResult();
BrowseResultToJUnitResult jres = new
BrowseResultToJUnitResult(tr);
jres.addBrowserResult(res);
assertEquals(8, tr.runCount());
assertEquals(0, tr.errorCount());
assertEquals(1, tr.failureCount());
}
private String xmlAsString(String xml) throws IOException {
String value;
InputStream is = getClass().getResourceAsStream(xml);
ByteArrayOutputStream bos = new
ByteArrayOutputStream();
byte[] data = new byte[1024];
int ln = 0;
while ((ln = is.read(data, 0, 1024)) != -1) {
Diferent build definitions with project group build all
Hi: We have several maven 2 projects without modules that i would like to run secuentally in the correct dependency order, if i create a project group for them and use the build all feature continumm resolves the order and invokes the default build definition for every project secuentially, but it seems that i can have only one default build definition for all the projects, the project group default build definition. Can i configure a default build definition not for project group but for project? I need to invoke diferent goals on every project, for example on one project i must deploy to jboss while in another i must use a ftp plugin i,ve created and so on ... i don´t need more than one build definition for project but all build definitions must be diferent and i need to invoke them through the build all button so i can´t create diferent groups for every project. best regards, Raul -- This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente. Pueden estar protegidos por secreto profesional Si usted recibe este correo electronico por error, gracias de informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos Origin no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos Origin, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus --
Re: Downloading dependency sources
You can add sources to the dependency. If you need the classes jar too, then you should have the dependency twice in your dependency list. Nicole On 10/22/07, Paul Gier <[EMAIL PROTECTED]> wrote: > > Hi Everyone, > Is there a way to tell maven to download source jars by default? I didn't > see > anything in the pom or settings model to do this. I know I can download > sources > using the eclipse plugin or the dependency plugin, but I would like to > tell > maven to always download source jars when building a project. > > Thanks! > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
problem with version ranges
hi, i am working with version ranges, which is making problems. if i mark a version range like [1.0,) and there is only 2.0 and no 1.0 version in my local repository, maven gives me an error that it cannot find range [1.0,). if i download 1.0 version it goes fine. i would expect that maven just picks the version of the local repository as long as it is included in the range. or am i misguided? thanks. -- View this message in context: http://www.nabble.com/problem-with-version-ranges-tf4671291s177.html#a13344785 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Java doc generation
On 10/20/07, Vincent Siveton <[EMAIL PROTECTED]> wrote: > Hi, > > The problems should be fixed in svn. Could you try again with a > SNAPSHOT version? Vincent, did you release a new snapshot after making those changes ? The last since to be from the 11th of Octover: http://people.apache.org/repo/m2-snapshot-repository/org/apache/maven/plugins/maven-javadoc-plugin/2.4-SNAPSHOT/ (and I am now seeing MJAVADOC-156 on my projects) Cheers, jerome - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jsunit integration
I also got no reply to my request. jsunit (2.1) depends on jetty 4.2. I've asked the jetty guys to upload the requierd jars to there maven repo (will be sync to central). I'll ask to upload the jsunit artifacts as far as all dependencies are available. 2007/10/22, Harlan Iverson <[EMAIL PROTECTED]>: > > The recurring issue seems to be getting JSUnit dependencies from Maven. Is > there a dialog open with the JSUnit team about this? > > I've made an attempt but heard nothing: > http://tech.groups.yahoo.com/group/jsunit/message/954 > > In my opinion, the ideal solution would be to get JSUnit building with a > set > of dependencies are are compatible with that's in Maven central (adding > some > more if necessary, like start.jar for jetty5x), and itself deploying > artifact(s) of its own. > > I've myself started working on JSUnit's build.xml and to use Maven Antlib > and created a pom to do just that (I can send it to anyone who's > interested); I think the only thing it needs missing is start.jar. > > Here's relevant threads from the JSUnit list: > http://tech.groups.yahoo.com/group/jsunit/message/988 > > > I also think that Nico's approach of breaking jsunit-app into its own > artifact to run inside Jetty, merged with a project's test cases and > dependencies, is worth looking more at. > > Harlan > > On 10/22/07, nicolas de loof <[EMAIL PROTECTED]> wrote: > > > > FYI I've started a javascript plugin project as part of maven Mojo. It > > allready support running jsunit tests : > > > > http://svn.codehaus.org/mojo/trunk/sandbox/javascript-maven-tools > > > > You can look at javascript-maven-plugin JsUnitMojo, that runs a > customized > > TestCase with a shared jsUnit server to avoid the server-per-test issue > > you > > noticed. > > > > You will not be able to run the plugin as many dependencies are not > (yet) > > available in central repo. > > You can look at the src/it projects on how to configure and use the > plugin > > for jsunit tests. > > > > Could you give me an example of the test result generated from jsunit > > result > > ? This part of the plugin is far perfectible, and I would welcome > > contribution ;-) > > > > Nico. > > > > > > 2007/10/22, Insitu <[EMAIL PROTECTED]>: > > > > > > Hello, > > > I am working on integrating jsunit ( http://www.jsunit.net) into > > > maven. I would like to share some thoughts and request some advices > > > avout the best way to do that integration. > > > > > > Right now, I have a sample (maven) project that executes jsunit tests > > > from maven and generates reports. What I did is: > > > - modify jsunit java server test cases to generate JUnit test results > > >from jsunit test results: That way javascript unit tests results > > >and error gets integrated seamlessly into surefire's reports > > > - package the java server as an artifact > > > - encapsulates all tests in a single JUnit tests cases that > > >configures things and laucn jsunit's StandaloneTest class > > > > > > Some problems are: > > > - test pages contains hardwired and absolute references to everything > > >(ie. scripts and jsunti base directory) which is BAD ! > > > - you need to install jsunit somewhere locally > > > - you need to modify and track files by hand outside of the scope of > > >the project > > > - test server is started once for each test execution or event each > > >JUnit test class execution which can be a performance bottleneck > > >for large and/or deep projects > > > > > > What I want to do is: > > > 1. package jsunit runner and support files as a jar or zip > > > 2. create a plugin tbound to process-test-sources that would unpack > > > the jsunit site in target/jsunit-runner > > > 3. configure generically test server/runners to have > > > target/jsunit-runner as their root site. This implies that > > > javascript source files, test files and test pages be moved to > > > this directory too... > > > > > > Ideally, I would rather serve everything from a servlet launched > > > through jetty with the adequate maven plugin but this would require > > > heavy changes to jsunit java server code. Or may be not... > > > > > > Comments and ideas are welcomed, > > > > > > regards, > > > -- > > > OQube < software engineering \ génie logiciel > > > > Arnaud Bailly, Dr. > > > \web> http://www.oqube.com > > > > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > >
Re: Java doc generation
Hi Jerome, Done right now. Cheers, Vincent 2007/10/22, Jerome Lacoste <[EMAIL PROTECTED]>: > On 10/20/07, Vincent Siveton <[EMAIL PROTECTED]> wrote: > > Hi, > > > > The problems should be fixed in svn. Could you try again with a > > SNAPSHOT version? > > Vincent, > > did you release a new snapshot after making those changes ? > > The last since to be from the 11th of Octover: > > http://people.apache.org/repo/m2-snapshot-repository/org/apache/maven/plugins/maven-javadoc-plugin/2.4-SNAPSHOT/ > > (and I am now seeing MJAVADOC-156 on my projects) > > Cheers, > > jerome > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Internal (company) repository layout best practices
we are not splitting repositories for releases and snapshots. in our case we are modularizing our "bigger" application to single maven artifacts, so when developing for a new release, changes (fixes, features) are often added often to more than one project. as soon there is a change we switch from release mode to snapshot mode for the new release. i think the main reason to split repositories is if you have got public libraries which external organisations/companies are using. i think in that case it is senseful to have a strict isolated view. but if you're developing for a new release and if you've got many modules, which are "forming one bigger" application i would not split repositories, because in that situation i do not want to have a separated snapshot vs. release view. the first post mentioned hygiene: i still look for a way to get an overview of the dependencies of all my internal modules (release or snapshot version). especially when working with lots of modules and still supporting older releases in branches an overview of module-couplings could be invaluable. i know that in the standard report of a project you can see the library-dependencies of one module. what i miss is the bigger pictures of the dependencies between all modules you are working on during development. -- View this message in context: http://www.nabble.com/Internal-%28company%29-repository-layout-best-practices-tf4645351s177.html#a13347335 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
stuck state when downloading snapshots
sometimes i am having problems with downloading snapshots. for instance when trying to download dependencies from an internal repository to local one the folder gets created like xxx/bla/1.0-SNAPSHOT but inside this folder i only see metadata.xml files. maven tells me a BUILD ERROR and says that xxx:bla:1.0-SNAPSHOT:jar could not be located. my workaround is to delete the complete bla/ folder and after that download goes fine. does anybody know something about this "stuck" download state or is there a special configuration to be done? this download behaviour is especially annoying for integration tools like cruise control which gives me work hindering wrong failure (false positive) messages. -- View this message in context: http://www.nabble.com/stuck-state-when-downloading-snapshots-tf4672399s177.html#a13348182 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Downloading dependency sources
> Is there a way to tell maven to download source jars by > default? I didn't see anything in the pom or settings model > to do this. I know I can download sources using the eclipse > plugin or the dependency plugin, but I would like to tell > maven to always download source jars when building a project. The dependency:sources goal will download the source jars for all dependencies. You could bind this into the lifecycle so it is run automatically. Of course, this only works on a project-by-project basis. ~Daniel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Diferent build definitions with project group build all
Raúl Arabaolaza Barquín a écrit : Hi: We have several maven 2 projects without modules that i would like to run secuentally in the correct dependency order, if i create a project group for them and use the build all feature continumm resolves the order and invokes the default build definition for every project secuentially, but it seems that i can have only one default build definition for all the projects, the project group default build definition. Can i configure a default build definition not for project group but for project? I need to invoke diferent goals on every project, for example on one project i must deploy to jboss while in another i must use a ftp plugin i,ve created and so on ... i don´t need more than one build definition for project but all build definitions must be diferent and i need to invoke them through the build all button so i can´t create diferent groups for every project. on each project, you can create a default build definition. It will be used in the build process instead of the one defined on the group. Emmanuel
Site Plugin 2.0-beta-6-SNAPSHOT ".vm" filtering fails now
Hi. I am having many troubles with the site plugin. One new one is in filtering. The last snapshot version of 2.0-beta-6 allowed naming the index page as "index.xml.vm" and this enabled filtering property values into the page. In the latest update, the generated Web page name has now become "index.xml.html" -- it used to be "index.html", which was correct. Anyone else see this problem? I'll try to file an issue. I'm having other problems too. I'll write up another post with a different subject for more questions there. Thanks! Ciao. Steev Coco. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Site Plugin 2.0-beta-6-SNAPSHOT ".vm" filtering fails now
This might be because of the fix for http://jira.codehaus.org/browse/DOXIA-161 Steven Coco wrote: Hi. I am having many troubles with the site plugin. One new one is in filtering. The last snapshot version of 2.0-beta-6 allowed naming the index page as "index.xml.vm" and this enabled filtering property values into the page. In the latest update, the generated Web page name has now become "index.xml.html" -- it used to be "index.html", which was correct. Anyone else see this problem? I'll try to file an issue. I'm having other problems too. I'll write up another post with a different subject for more questions there. Thanks! Ciao. Steev Coco. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Site Plugin 2.0-beta-6-SNAPSHOT ".vm" filtering fails now
I have now confirmed that this is the case. The fix for DOXIA-161 has been removed from svn and a new SNAPSHOT of doxia has been deployed. Please test that this solves your problem. Dennis Lundberg wrote: This might be because of the fix for http://jira.codehaus.org/browse/DOXIA-161 Steven Coco wrote: Hi. I am having many troubles with the site plugin. One new one is in filtering. The last snapshot version of 2.0-beta-6 allowed naming the index page as "index.xml.vm" and this enabled filtering property values into the page. In the latest update, the generated Web page name has now become "index.xml.html" -- it used to be "index.html", which was correct. Anyone else see this problem? I'll try to file an issue. I'm having other problems too. I'll write up another post with a different subject for more questions there. Thanks! Ciao. Steev Coco. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Site Plugin 2.0-beta-6-SNAPSHOT ".vm" filtering fails now
That fixed it: mvn -U -up clean site Back to the usual. Thanks. On Tue, 2007-10-23 at 00:03 +0200, Dennis Lundberg wrote: > I have now confirmed that this is the case. The fix for DOXIA-161 has > been removed from svn and a new SNAPSHOT of doxia has been deployed. > Please test that this solves your problem. > > Dennis Lundberg wrote: > > This might be because of the fix for > > http://jira.codehaus.org/browse/DOXIA-161 > > > > Steven Coco wrote: > >> Hi. > >> > >> I am having many troubles with the site plugin. One new one is in > >> filtering. The last snapshot version of 2.0-beta-6 allowed naming the > >> index page as "index.xml.vm" and this enabled filtering property values > >> into the page. In the latest update, the generated Web page name has now > >> become "index.xml.html" -- it used to be "index.html", which was > >> correct. > >> > >> Anyone else see this problem? I'll try to file an issue. > >> > >> I'm having other problems too. I'll write up another post with a > >> different subject for more questions there. > >> > >> Thanks! > >> > >> Ciao. > >> Steev Coco. > >> > >> > >> - > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > > > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: reading pom.version from a file
there is no right way to read the version from a file.. the pom is the file
that contains the version...
stop thinking like an ant script and start thinking like an OO programmer
BTW thats not meant to be critical or offensive just to catch your attention
and make you think...
On Tuesday 23 October 2007 03:47, baumar wrote:
t> Hi,
>
> What would be the right way to read the version number from a file?
>
> We decided that not all users (who maybe don't know maven very well) should
> check out the delicate pom file .
> We have a file like version.properties containing
>
> tavx.current.version=1.2.3a
>
> and defined in the pom
>
>
> 4.0.0
> com.abc.tat.tavx
> tavx
> adapter
> jar
> ${tavx.current.version}
> ...
>
>
> src/resources/version/version.properties
>
>
> but that doesn't work.
>
>
> Thanks for help
>
> Markus
--
Michael McCallum
Enterprise Engineer
mailto:[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
