Re: Variables interpolation: dynamic in Maven 2, static in Maven 3 ?
I'll watch this issue as I'm really interested in how it might be handled.
Personally I don't have a clear position here.
Sometimes I'd like the property interpolation to be a little more
dynamic. It would e.g. be great if I could activate a profile by the
existence of a file whose path contains an interpolatable token (like
'src/main/filters/${target.environment}/something.properties'). But I
understand that something like this might lead to confusing
interpolation behaviour which sometimes could be hard to maintain. Like
Luke wrote, those build configurations would be less declarative.
What about introducing something like property scopes and/or types?
properties
my-prop scope=... type=...foo/my-prop
!-- 'scope' = 'global|pom' --
!-- 'type' = 'mutable|immutable' --
/properties
This was just a spontaneous idea, not really well-thought (yet).
On 28/01/11 18:11, Evgeny Goldin wrote:
Created an issue:http://jira.codehaus.org/browse/MNG-4998
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Regarding Automating Deployment to JBoss from Nexus
Hi All, Currently I am able to build my artifacts using Maven and successfully published to Nexus repository. I want to deploy deploy the war files and other configuration zip files from Nexus to the remote Jboss server. I have few doubts regarding this. 1)Can I use separate pom.xml file for my deployment activity, where I will be mentioning the path of the files from Nexus and path of deployment. 2)If I have to use the same pom.xml (which is my projects pom), then how can I pick the artifact directly from Nexus repository without looking in local repo or target folder. I had a glance of JBoss plugins and Cargo plugin. But unable to understand how to pick the war/conf files from my Nexus repo where I published previously. Regards, Tirumal Reddy M
Re: Regarding Automating Deployment to JBoss from Nexus
not quite the solution you are looking for but have a look at the ship-maven-plugin @ mojo On 31 January 2011 11:17, Tirumal Reddy Moolamalla t.moolama...@zensar.com wrote: Hi All, Currently I am able to build my artifacts using Maven and successfully published to Nexus repository. I want to deploy deploy the war files and other configuration zip files from Nexus to the remote Jboss server. I have few doubts regarding this. 1) Can I use separate pom.xml file for my deployment activity, where I will be mentioning the path of the files from Nexus and path of deployment. 2) If I have to use the same pom.xml (which is my projects pom), then how can I pick the artifact directly from Nexus repository without looking in local repo or target folder. I had a glance of JBoss plugins and Cargo plugin. But unable to understand how to pick the war/conf files from my Nexus repo where I published previously. Regards, Tirumal Reddy M - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Error while compiling : annotations are not supported in -source 1.3
I am now running Maven 3 . and the mvn compile is successful . Hence It's got something to do with my lack of provisioning for Maven 2 However I am still getting another error when I tried to run the main class with Derby(with your suggestion on persistence taken into account) . I am making a new Post on that regard, as Its a different command. -- View this message in context: http://maven.40175.n5.nabble.com/Error-while-compiling-annotations-are-not-supported-in-source-1-3-tp3343153p3364438.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: Site plugin - broken links between modules only on site stage
Which version of the site plugin are you using (it's not specified in your poms)? Please test 2.3-SNAPSHOT, some staging issues should be fixed with http://jira.codehaus.org/browse/MSITE-533. HTH, -Lukas Marcin Kuthan wrote: Hi My multi module project is structured with separate aggregate pom and parent pom (aggregate pom is not a parent pom). All modules are aggregated by aggragate pom (parent pom is also submodule of aggregate pom). All submodules inherit from parent pom. Aggregate pom: http://code.google.com/p/m4enterprise/source/browse/trunk/modular-war/pom.xml Parent pom: http://code.google.com/p/m4enterprise/source/browse/trunk/modular-war/modular-war-parent/pom.xml And other submodules: http://code.google.com/p/m4enterprise/source/browse/trunk/modular-war/modular-war-core/pom.xml http://code.google.com/p/m4enterprise/source/browse/trunk/modular-war/modular-war-webapp/pom.xml For all modulesurl are defined to reflect project structure. When the site is deployed (mvn site-deploy) links between modules are valid, but for site stage (mvn site:stage or mvn site:stage-deploy) are broken. It looks that relative links point one directory level too high. In the index page of aggregate pom the link to the parent module looks like: ../../../../../my-site-url-from-dist-management-section/modular-war-parent/index.html If I change it to (remove one directory level): ../../../../my-site-url-from-dist-management-section/modular-war-parent/index.html link is valid. Links to modular-war-parent from modular-war-core and modular-war-webapp are valid, e.g: ../index.html, only links from aggregate pom to submodules are broken. I tried to remove trailing slashes fromurl element but it didn't help, the links were unchanged. Do you have an idea where is a mistake in my configuration? And why links are broken only for site stage, when for regular site deployment are valid? Thanks, Marcin - 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
failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2:java
This is the command I typed to run the main class with derby :
mvn exec:java -Dexec.mainClass=com.apress.javaee6.chapter02.Main
Following is the image of my command prompt
http://maven.40175.n5.nabble.com/file/n3364506/maven.jpg
I have uploaded my project in rapidshare
http://rapidshare.com/files/445466516/je.zip
http://rapidshare.com/files/445466516/je.zip . {just to help in the error
detection process}
FYI, I'm using Maven 3.0.2.
Regards,
Ankur.
--
View this message in context:
http://maven.40175.n5.nabble.com/failed-to-execute-goal-org-codehaus-mojo-exec-maven-plugin-1-2-java-tp3364506p3364506.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: Variables interpolation: dynamic in Maven 2, static in Maven 3 ?
Hi Marc, Marc Rohlfs wrote: What about introducing something like property scopes and/or types? properties my-prop scope=... type=...foo/my-prop !-- 'scope' = 'global|pom' -- !-- 'type' = 'mutable|immutable' -- /properties This was just a spontaneous idea, not really well-thought (yet). Like it, can work really well. Default behavior (no additional attributes) can be more conservative Ant-like static interpolation but with additional attributes dynamic interpolation can be turned on. I suggest interpolation=static|dynamic attribute. I checked Maven 2 compatibility now, it works Ok, it ignores additional attributes: properties propName a=a b=ccpropValue/propName - Best regards, Evgeny http://evgeny-goldin.com/ evgeny-goldin.com -- View this message in context: http://maven.40175.n5.nabble.com/Variables-interpolation-dynamic-in-Maven-2-static-in-Maven-3-tp3360336p3364531.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: Variables interpolation: dynamic in Maven 2, static in Maven 3 ?
Marc Rohlfs wrote:
... It would e.g. be great if I could activate a profile by the
existence of a file whose path contains an interpolatable token (like
'src/main/filters/${target.environment}/something.properties'). But I
understand that something like this might lead to confusing
interpolation behaviour which sometimes could be hard to maintain.
I think you're right to be concerned about adding extra confusion. My guess
is that the only way something like this can have a chance is if the target
is limited to the configuration section of plugins. i.e. nothing that
affects the build plan?
I'm a little worried that this discussion will quickly be gaftered if the
scope gets too scary or ambitious.
Hog wild sidenote: it would be nice if configuration sections could
contain portions that were dynamically generated by other plugins, why stop
at simple properties?
--
View this message in context:
http://maven.40175.n5.nabble.com/Variables-interpolation-dynamic-in-Maven-2-static-in-Maven-3-tp3360336p3364574.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: Site plugin - broken links between modules only on site stage
Hi Lukas
I'm sorry that I didn't specify versions in the first post. I tested
my poms with version 2.2 (for Maven 2.2.1) and version 3.0-beta-3 (for
Maven 3.0.2). In both cases links are invalid.
I updated my build to 2.3-SNAPSHOT and plugin reported invalid
character in url element. There was a mistake in property name, and
literal value ${prop} was used instead of interpreted value. The new
plugin versions helped me to find out this bug - great!
I checked again version 2.2, even with fixed property name links in
the project stage are still invalid.
For version 2.3-SNAPSHOT it seems to be almost ok. The depth of
directory levels in the links is now correct but it looks that
distributionManagement.site.url is not resolved correctly.
Please look at
http://code.google.com/p/m4enterprise/source/browse/trunk/corporate-pom/pom.xml.
Element distributionManagement.site.url is set as a property
${com.acme.maven.corporate-pom.distributionManagement.siteUrl}.
Default value of the property is
scp://sites.intranet.acme.com/var/www. In my settings.xml I
overwrite this property with scp://sites.my-company.com/var/www.
As a result: stage is generated into
target/staging/sites.my-company.com/var/www directory, but the links
look like
../../../../sites.intranet.acme.com/var/www/modular-war-parent/index.html
There is no sites.intranet.acme.com elements in the effective pom of
the project, variables are resolved correctly to values from
settings.xml.
Could you check for differences between directory structure and links
generation for 2.3-SNAPSHOT, please? Are they generated in the similar
way?
Many Thanks,
Marcin
On 31 January 2011 14:04, Lukas Theussl ltheu...@apache.org wrote:
Which version of the site plugin are you using (it's not specified in your
poms)? Please test 2.3-SNAPSHOT, some staging issues should be fixed with
http://jira.codehaus.org/browse/MSITE-533.
HTH,
-Lukas
Marcin Kuthan wrote:
Hi
My multi module project is structured with separate aggregate pom and
parent pom (aggregate pom is not a parent pom).
All modules are aggregated by aggragate pom (parent pom is also
submodule of aggregate pom). All submodules inherit from parent pom.
Aggregate pom:
http://code.google.com/p/m4enterprise/source/browse/trunk/modular-war/pom.xml
Parent pom:
http://code.google.com/p/m4enterprise/source/browse/trunk/modular-war/modular-war-parent/pom.xml
And other submodules:
http://code.google.com/p/m4enterprise/source/browse/trunk/modular-war/modular-war-core/pom.xml
http://code.google.com/p/m4enterprise/source/browse/trunk/modular-war/modular-war-webapp/pom.xml
For all modulesurl are defined to reflect project structure. When
the site is deployed (mvn site-deploy) links between modules are
valid, but for site stage (mvn site:stage or mvn site:stage-deploy)
are broken.
It looks that relative links point one directory level too high. In
the index page of aggregate pom the link to the parent module looks
like:
../../../../../my-site-url-from-dist-management-section/modular-war-parent/index.html
If I change it to (remove one directory level):
../../../../my-site-url-from-dist-management-section/modular-war-parent/index.html
link is valid.
Links to modular-war-parent from modular-war-core and
modular-war-webapp are valid, e.g: ../index.html, only links from
aggregate pom to submodules are broken.
I tried to remove trailing slashes fromurl element but it didn't
help, the links were unchanged.
Do you have an idea where is a mistake in my configuration? And why
links are broken only for site stage, when for regular site deployment
are valid?
Thanks,
Marcin
-
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
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Site plugin - broken links between modules only on site stage
This sounds like a manifestation of
http://jira.codehaus.org/browse/MSITE-135 but I'm not sure. If you can
attach a simple test project that would help, I haven't tried to fix
this yet.
-Lukas
Marcin Kuthan wrote:
Hi Lukas
I'm sorry that I didn't specify versions in the first post. I tested
my poms with version 2.2 (for Maven 2.2.1) and version 3.0-beta-3 (for
Maven 3.0.2). In both cases links are invalid.
I updated my build to 2.3-SNAPSHOT and plugin reported invalid
character inurl element. There was a mistake in property name, and
literal value ${prop} was used instead of interpreted value. The new
plugin versions helped me to find out this bug - great!
I checked again version 2.2, even with fixed property name links in
the project stage are still invalid.
For version 2.3-SNAPSHOT it seems to be almost ok. The depth of
directory levels in the links is now correct but it looks that
distributionManagement.site.url is not resolved correctly.
Please look at
http://code.google.com/p/m4enterprise/source/browse/trunk/corporate-pom/pom.xml.
Element distributionManagement.site.url is set as a property
${com.acme.maven.corporate-pom.distributionManagement.siteUrl}.
Default value of the property is
scp://sites.intranet.acme.com/var/www. In my settings.xml I
overwrite this property with scp://sites.my-company.com/var/www.
As a result: stage is generated into
target/staging/sites.my-company.com/var/www directory, but the links
look like
../../../../sites.intranet.acme.com/var/www/modular-war-parent/index.html
There is no sites.intranet.acme.com elements in the effective pom of
the project, variables are resolved correctly to values from
settings.xml.
Could you check for differences between directory structure and links
generation for 2.3-SNAPSHOT, please? Are they generated in the similar
way?
Many Thanks,
Marcin
On 31 January 2011 14:04, Lukas Theusslltheu...@apache.org wrote:
Which version of the site plugin are you using (it's not specified in your
poms)? Please test 2.3-SNAPSHOT, some staging issues should be fixed with
http://jira.codehaus.org/browse/MSITE-533.
HTH,
-Lukas
Marcin Kuthan wrote:
Hi
My multi module project is structured with separate aggregate pom and
parent pom (aggregate pom is not a parent pom).
All modules are aggregated by aggragate pom (parent pom is also
submodule of aggregate pom). All submodules inherit from parent pom.
Aggregate pom:
http://code.google.com/p/m4enterprise/source/browse/trunk/modular-war/pom.xml
Parent pom:
http://code.google.com/p/m4enterprise/source/browse/trunk/modular-war/modular-war-parent/pom.xml
And other submodules:
http://code.google.com/p/m4enterprise/source/browse/trunk/modular-war/modular-war-core/pom.xml
http://code.google.com/p/m4enterprise/source/browse/trunk/modular-war/modular-war-webapp/pom.xml
For all modulesurlare defined to reflect project structure. When
the site is deployed (mvn site-deploy) links between modules are
valid, but for site stage (mvn site:stage or mvn site:stage-deploy)
are broken.
It looks that relative links point one directory level too high. In
the index page of aggregate pom the link to the parent module looks
like:
../../../../../my-site-url-from-dist-management-section/modular-war-parent/index.html
If I change it to (remove one directory level):
../../../../my-site-url-from-dist-management-section/modular-war-parent/index.html
link is valid.
Links to modular-war-parent from modular-war-core and
modular-war-webapp are valid, e.g: ../index.html, only links from
aggregate pom to submodules are broken.
I tried to remove trailing slashes fromurlelement but it didn't
help, the links were unchanged.
Do you have an idea where is a mistake in my configuration? And why
links are broken only for site stage, when for regular site deployment
are valid?
Thanks,
Marcin
-
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
-
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: surefire classpath problems with maven 3 parallel
With further analyzing I found that in case of the error (ClassNotFound) the corresponding JAR file is really missing in the compiler class path while the test classes are compiled. On some build runs, the junit jar was not in the compiler classpath, on some other build runs, the mockito jar file was not in the classpath. Sometimes both are missing. But sometimes a project which faild on a build, runs ok when I try it again and it fails later on a different project - but always with the same classpath problems. I found this problems only on compiling test-classes, never on non test classes. In the meantime someone opened a bug at codehouse which seems to describe the same (or nearly the same) problem: http://jira.codehaus.org/browse/MNG-4996?focusedCommentId=253613#action_253613 Thanks for your help, Frank -- View this message in context: http://maven.40175.n5.nabble.com/surefire-classpath-problems-with-maven-3-parallel-tp3346469p3364711.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
[ANN] LaTeX Maven Mojo 1.1 Released
Hi, The Mojo team is pleased to announce the release of the Mojo Latex Maven Plugin version 1.1. The LaTeX Maven Mojo is useful for building a set of LaTeX documents. It builds PDF documents using pdflatex, and has optional support for bibtex. http://mojo.codehaus.org/latex-maven-plugin/ To get this update, simply specify the version in your project's plugin configuration: plugin groupIdorg.codehaus.mojo/groupId artifactIdlatex-maven-plugin/artifactId version1.1/version /plugin Release Notes The following issues have been solved: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12077version=16250 The main improvements are: * support for --shell-escape which is needed when external tools shall be used by pdflatex * the compilation is now dependent on files having been modified since the last build * .svn folders are not copied to target/ when the compilation occurs. Enjoy, The Mojo team. Julien Ponge -- http://izpack.org/ http://jpz-log.info/ http://julien.ponge.info/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to build plugin before top-level project uses it
I am new to maven. I have a top level project with several sub-projects below it. I have recently created a plugin as a sub-project that will be used by the top level project during the build (packaging phase most likely). I am having trouble getting maven to build the plugin and install it into the repository before the top level project needs it. It seems that as soon as the top level project sees the requirement for the plugin, it attempts to get it from the repository, which of course fails since it's not there yet. You can see it listed as the second item in the reactor order just under the top level project. If I try adding the plugin as a dependency of the top level POM, I get a cyclic reference error. I also tried adding as a dependency to one of the subprojects, it still gives an error stating that it's not in the repository. Anyway, what’s the best way to go about doing this? If I build the plugin separately, then run the entire build, it works fine. How can I get maven to do something like that but without two separate builds? Thanks, Dave
Re: How to build plugin before top-level project uses it
On 31 January 2011 09:53, E S electric.or.sh...@gmail.com wrote: Anyway, what’s the best way to go about doing this? If I build the plugin separately, then run the entire build, it works fine. How can I get maven to do something like that but without two separate builds? Why don't you put it in a separate project? Run mvn install or mvn deploy once and your plugin is available to all of your projects. No need to build it again. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to build plugin before top-level project uses it
That's certainly an option, but it doesn't work as well as I would like for our build server or new developers getting their dev environments set up. We could get around it using something like build script on top of maven, but I would prefer a cleaner solution in which maven handles it automatically if possible. On Mon, Jan 31, 2011 at 12:00 PM, Hilco Wijbenga hilco.wijbe...@gmail.comwrote: On 31 January 2011 09:53, E S electric.or.sh...@gmail.com wrote: Anyway, what’s the best way to go about doing this? If I build the plugin separately, then run the entire build, it works fine. How can I get maven to do something like that but without two separate builds? Why don't you put it in a separate project? Run mvn install or mvn deploy once and your plugin is available to all of your projects. No need to build it again. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to build plugin before top-level project uses it
you cannot use a plugin within the same reactor as the plugin is built from. this is usually solved in one of two ways: 1. use the immediately previous release of the plugin, so the reactor build version 1.1-SNAPSHOT but uses version 1.0 2. move the plugin to its own reactor the reason why this is required is that a plugin can change the build plan, and the build plan must be constructed before you start building - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 31 Jan 2011 17:54, E S electric.or.sh...@gmail.com wrote:
Re: Site plugin - broken links between modules only on site stage
Hi Lukas
I don't think that my findings are related to MSITE-135. Only
2.3-SNAPSHOT is affected.
You should reproduce the issue in 10 mins:
1. Follow http://code.google.com/p/m4enterprise/wiki/GettingStarted
(only Checkout Source Code and Install Corporate POM sections)
2. Go to trunk/modular-war
3. Call:
mvn clean
mvn -Dcom.acme.maven.corporate-pom.siteVersion=2.3-SNAPSHOT
-Dcom.acme.maven.corporate-pom.enforcerRulesDisabled site:site
site:stage
4. Call:
mvn clean
mvn -Dcom.acme.maven.corporate-pom.siteVersion=2.3-SNAPSHOT
-Dcom.acme.maven.corporate-pom.enforcerRulesDisabled site:site
site:stage
-Dcom.acme.maven.corporate-pom.distributionManagement.siteUrl=scp://host/var/www
For 3) generated stage are fine, links in modular-war to submodules are valid.
For 4) links are broken,
com.acme.maven.corporate-pom.distributionManagement.siteUrl property
is ignored
If you use
-Dcom.acme.maven.corporate-pom.distributionManagement.siteUrl=file:///home/
results are even worse. URLs are totally broken.
Marcin
On 31 January 2011 16:32, Lukas Theussl ltheu...@apache.org wrote:
This sounds like a manifestation of
http://jira.codehaus.org/browse/MSITE-135 but I'm not sure. If you can
attach a simple test project that would help, I haven't tried to fix this
yet.
-Lukas
Marcin Kuthan wrote:
Hi Lukas
I'm sorry that I didn't specify versions in the first post. I tested
my poms with version 2.2 (for Maven 2.2.1) and version 3.0-beta-3 (for
Maven 3.0.2). In both cases links are invalid.
I updated my build to 2.3-SNAPSHOT and plugin reported invalid
character inurl element. There was a mistake in property name, and
literal value ${prop} was used instead of interpreted value. The new
plugin versions helped me to find out this bug - great!
I checked again version 2.2, even with fixed property name links in
the project stage are still invalid.
For version 2.3-SNAPSHOT it seems to be almost ok. The depth of
directory levels in the links is now correct but it looks that
distributionManagement.site.url is not resolved correctly.
Please look at
http://code.google.com/p/m4enterprise/source/browse/trunk/corporate-pom/pom.xml.
Element distributionManagement.site.url is set as a property
${com.acme.maven.corporate-pom.distributionManagement.siteUrl}.
Default value of the property is
scp://sites.intranet.acme.com/var/www. In my settings.xml I
overwrite this property with scp://sites.my-company.com/var/www.
As a result: stage is generated into
target/staging/sites.my-company.com/var/www directory, but the links
look like
../../../../sites.intranet.acme.com/var/www/modular-war-parent/index.html
There is no sites.intranet.acme.com elements in the effective pom of
the project, variables are resolved correctly to values from
settings.xml.
Could you check for differences between directory structure and links
generation for 2.3-SNAPSHOT, please? Are they generated in the similar
way?
Many Thanks,
Marcin
On 31 January 2011 14:04, Lukas Theusslltheu...@apache.org wrote:
Which version of the site plugin are you using (it's not specified in
your
poms)? Please test 2.3-SNAPSHOT, some staging issues should be fixed with
http://jira.codehaus.org/browse/MSITE-533.
HTH,
-Lukas
Marcin Kuthan wrote:
Hi
My multi module project is structured with separate aggregate pom and
parent pom (aggregate pom is not a parent pom).
All modules are aggregated by aggragate pom (parent pom is also
submodule of aggregate pom). All submodules inherit from parent pom.
Aggregate pom:
http://code.google.com/p/m4enterprise/source/browse/trunk/modular-war/pom.xml
Parent pom:
http://code.google.com/p/m4enterprise/source/browse/trunk/modular-war/modular-war-parent/pom.xml
And other submodules:
http://code.google.com/p/m4enterprise/source/browse/trunk/modular-war/modular-war-core/pom.xml
http://code.google.com/p/m4enterprise/source/browse/trunk/modular-war/modular-war-webapp/pom.xml
For all modulesurl are defined to reflect project structure. When
the site is deployed (mvn site-deploy) links between modules are
valid, but for site stage (mvn site:stage or mvn site:stage-deploy)
are broken.
It looks that relative links point one directory level too high. In
the index page of aggregate pom the link to the parent module looks
like:
../../../../../my-site-url-from-dist-management-section/modular-war-parent/index.html
If I change it to (remove one directory level):
../../../../my-site-url-from-dist-management-section/modular-war-parent/index.html
link is valid.
Links to modular-war-parent from modular-war-core and
modular-war-webapp are valid, e.g: ../index.html, only links from
aggregate pom to submodules are broken.
I tried to remove trailing slashes fromurl element but it didn't
help, the links were unchanged.
Do you have an idea where is a mistake in my configuration? And why
links are broken only for site stage, when for regular site deployment
are
Re: How to build plugin before top-level project uses it
Well, using a previous version of the plugin isn't an option since one doesn't exist. As for using it in a separate reactor, are you saying you can somehow have multiple reactors during a single build? Can you point me to further information on that subject? Or did you just mean running a separate build of the plugin first like Hilco suggested? On Mon, Jan 31, 2011 at 12:11 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: you cannot use a plugin within the same reactor as the plugin is built from. this is usually solved in one of two ways: 1. use the immediately previous release of the plugin, so the reactor build version 1.1-SNAPSHOT but uses version 1.0 2. move the plugin to its own reactor the reason why this is required is that a plugin can change the build plan, and the build plan must be constructed before you start building - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 31 Jan 2011 17:54, E S electric.or.sh...@gmail.com wrote:
Re: How to build plugin before top-level project uses it
On 31 January 2011 10:08, E S electric.or.sh...@gmail.com wrote: That's certainly an option, but it doesn't work as well as I would like for our build server or new developers getting their dev environments set up. We could get around it using something like build script on top of maven, but I would prefer a cleaner solution in which maven handles it automatically if possible. How would any of this affect your build server or new developers? Just deploy the plugin once and it's available to everyone. You do have a place to deploy artifacts, right? If you don't then I would strongly suggest you set that up ASAP. (It's pretty simple.) I think you'll find that Maven doesn't scale very well without it so you're going to need it eventually anyway. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Basic POM Error: Project not Start_tag or End-Tag
Hi, I am getting an error for the very first word in my POM. I'm new to trying to really understand Maven because I have to modify a POM to do things together that I can't find a model for, Maven + Spring + web app. I used my IDE, IDEA, to create a basic project including a POM but IDEA is complaining about basic elements of the POM. The error on the very first word of the file is Expected START_TAG or END_TAG not TEST (position: TEXT seen.../dependency...d... I've used Maven before with a POM, and have no idea why this file has errors in it. Here is the entire thing. project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd; modelVersion4.0.0/modelVersion groupIdedu.apu.mvnspringwebapp/groupId artifactIdMvnSpringWebApp/artifactId packagingwar/packaging version1.0/version nameMvnSpringWebApp/name urlhttp://maven.apache.org/url dependencies dependency groupIdorg.springframework/groupId artifactIdspring-core/artifactId version3.0.0.RELEASE/version /dependency dependency groupIdorg.springframework/groupId artifactIdspring-expression/artifactId version3.0.0.RELEASE/version /dependency dependency groupIdorg.springframework/groupId artifactIdspring-beans/artifactId version3.0.0.RELEASE/version /dependency dependency groupIdorg.springframework/groupId artifactIdspring-webmvc/artifactId version3.0.0.RELEASE/version /dependency dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version scopetest/scope /dependency dependency groupIdlog4j/groupId artifactIdlog4j/artifactId version1.2.12/version /dependency - dependency groupIdcommons-logging/groupId artifactIdcommons-logging/artifactId version1.0.4/version /dependency - dependency groupIdapu-db/groupId artifactIdapu-db/artifactId versionSNAPSHOT/version /dependency /dependencies build finalNameMvnSpringWebApp/finalName /build /project Everything here was either generated by IDEA or I got it from a tutorial on Spring or Maven. Thanks. Ken Kenneth D. Litwak, Ph.D. Azusa Pacific University 901 E. Alosta Ave. Azusa, CA 91702 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Basic POM Error: Project not Start_tag or End-Tag
Perhaps the - before and after the commons-logging dependency? /Ludwig From: Kenneth Litwak [mailto:klit...@apu.edu] Sent: den 31 januari 2011 19:36 To: users@maven.apache.org Subject: Basic POM Error: Project not Start_tag or End-Tag Hi, I am getting an error for the very first word in my POM. I'm new to trying to really understand Maven because I have to modify a POM to do things together that I can't find a model for, Maven + Spring + web app. I used my IDE, IDEA, to create a basic project including a POM but IDEA is complaining about basic elements of the POM. The error on the very first word of the file is Expected START_TAG or END_TAG not TEST (position: TEXT seen.../dependency...d... I've used Maven before with a POM, and have no idea why this file has errors in it. Here is the entire thing. project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd; modelVersion4.0.0/modelVersion groupIdedu.apu.mvnspringwebapp/groupId artifactIdMvnSpringWebApp/artifactId packagingwar/packaging version1.0/version nameMvnSpringWebApp/name urlhttp://maven.apache.org/url dependencies dependency groupIdorg.springframework/groupId artifactIdspring-core/artifactId version3.0.0.RELEASE/version /dependency dependency groupIdorg.springframework/groupId artifactIdspring-expression/artifactId version3.0.0.RELEASE/version /dependency dependency groupIdorg.springframework/groupId artifactIdspring-beans/artifactId version3.0.0.RELEASE/version /dependency dependency groupIdorg.springframework/groupId artifactIdspring-webmvc/artifactId version3.0.0.RELEASE/version /dependency dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version scopetest/scope /dependency dependency groupIdlog4j/groupId artifactIdlog4j/artifactId version1.2.12/version /dependency - dependency groupIdcommons-logging/groupId artifactIdcommons-logging/artifactId version1.0.4/version /dependency - dependency groupIdapu-db/groupId artifactIdapu-db/artifactId versionSNAPSHOT/version /dependency /dependencies build finalNameMvnSpringWebApp/finalName /build /project Everything here was either generated by IDEA or I got it from a tutorial on Spring or Maven. Thanks. Ken Kenneth D. Litwak, Ph.D. Azusa Pacific University 901 E. Alosta Ave. Azusa, CA 91702 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org _ No virus found in this message. Checked by AVG - www.avg.com Version: 10.0.1204 / Virus Database: 1435/3414 - Release Date: 01/31/11
Re: How to build plugin before top-level project uses it
Yes, using our shared repository would be another option. We would have to maintain the plugin as if it were more like a 3rd party resource rather than part of the product's source, but maybe that's the right way to think about. Not sure, but if it works, I think that's fine. Thanks for the help. On Mon, Jan 31, 2011 at 12:25 PM, Hilco Wijbenga hilco.wijbe...@gmail.comwrote: On 31 January 2011 10:08, E S electric.or.sh...@gmail.com wrote: That's certainly an option, but it doesn't work as well as I would like for our build server or new developers getting their dev environments set up. We could get around it using something like build script on top of maven, but I would prefer a cleaner solution in which maven handles it automatically if possible. How would any of this affect your build server or new developers? Just deploy the plugin once and it's available to everyone. You do have a place to deploy artifacts, right? If you don't then I would strongly suggest you set that up ASAP. (It's pretty simple.) I think you'll find that Maven doesn't scale very well without it so you're going to need it eventually anyway. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Basic POM Error: Project not Start_tag or End-Tag
Ludwig, Thanks. Yes, that did it. Ken Kenneth D. Litwak, Ph.D. Azusa Pacific University 901 E. Alosta Ave. Azusa, CA 91702 -Original Message- From: Ludwig Magnusson [mailto:lud...@itcatapult.com] Sent: Monday, January 31, 2011 10:40 AM To: 'Maven Users List' Subject: RE: Basic POM Error: Project not Start_tag or End-Tag Perhaps the - before and after the commons-logging dependency? /Ludwig From: Kenneth Litwak [mailto:klit...@apu.edu] Sent: den 31 januari 2011 19:36 To: users@maven.apache.org Subject: Basic POM Error: Project not Start_tag or End-Tag Hi, I am getting an error for the very first word in my POM. I'm new to trying to really understand Maven because I have to modify a POM to do things together that I can't find a model for, Maven + Spring + web app. I used my IDE, IDEA, to create a basic project including a POM but IDEA is complaining about basic elements of the POM. The error on the very first word of the file is Expected START_TAG or END_TAG not TEST (position: TEXT seen.../dependency...d... I've used Maven before with a POM, and have no idea why this file has errors in it. Here is the entire thing. project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd; modelVersion4.0.0/modelVersion groupIdedu.apu.mvnspringwebapp/groupId artifactIdMvnSpringWebApp/artifactId packagingwar/packaging version1.0/version nameMvnSpringWebApp/name urlhttp://maven.apache.org/url dependencies dependency groupIdorg.springframework/groupId artifactIdspring-core/artifactId version3.0.0.RELEASE/version /dependency dependency groupIdorg.springframework/groupId artifactIdspring-expression/artifactId version3.0.0.RELEASE/version /dependency dependency groupIdorg.springframework/groupId artifactIdspring-beans/artifactId version3.0.0.RELEASE/version /dependency dependency groupIdorg.springframework/groupId artifactIdspring-webmvc/artifactId version3.0.0.RELEASE/version /dependency dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version scopetest/scope /dependency dependency groupIdlog4j/groupId artifactIdlog4j/artifactId version1.2.12/version /dependency - dependency groupIdcommons-logging/groupId artifactIdcommons-logging/artifactId version1.0.4/version /dependency - dependency groupIdapu-db/groupId artifactIdapu-db/artifactId versionSNAPSHOT/version /dependency /dependencies build finalNameMvnSpringWebApp/finalName /build /project Everything here was either generated by IDEA or I got it from a tutorial on Spring or Maven. Thanks. Ken Kenneth D. Litwak, Ph.D. Azusa Pacific University 901 E. Alosta Ave. Azusa, CA 91702 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org _ No virus found in this message. Checked by AVG - www.avg.com Version: 10.0.1204 / Virus Database: 1435/3414 - Release Date: 01/31/11 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Error building simple web project
I'm writing a web app with Maven and learning as I go. The packaging is war. I have a directory within my project that has the web pieces: web src main webapp WEB-INF Web.xml When I run mvn clean package, I get this error: [Info] Error assembling WAR: webxml element is required (or pre-exisitng WEB-INF/web.xml if executing in update mode) I assume there's something simple I haven't seen in the doc yet, but I'm reading through the POM reference and haven't seen it yet. What might be wrong? Thanks. Ken - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Error building simple web project
On 31 January 2011 13:08, Kenneth Litwak klit...@apu.edu wrote: I'm writing a web app with Maven and learning as I go. The packaging is war. I have a directory within my project that has the web pieces: web src main webapp WEB-INF Web.xml Is this just a copy-and-paste thing or did you really name it Web.xml? It should be web.xml (all lowercase). - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to build plugin before top-level project uses it
I thought this was possible with Maven 3.0, but not with Maven 2.x. Am I wrong? /Anders On Mon, Jan 31, 2011 at 19:11, Stephen Connolly stephen.alan.conno...@gmail.com wrote: you cannot use a plugin within the same reactor as the plugin is built from. this is usually solved in one of two ways: 1. use the immediately previous release of the plugin, so the reactor build version 1.1-SNAPSHOT but uses version 1.0 2. move the plugin to its own reactor the reason why this is required is that a plugin can change the build plan, and the build plan must be constructed before you start building - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 31 Jan 2011 17:54, E S electric.or.sh...@gmail.com wrote:
RE: Error building simple web project
Sorry, just a copy-and-paste error. I know the real thing has to have all lower-case. WEB-INF/web.xml Kenneth D. Litwak, Ph.D. Azusa Pacific University 901 E. Alosta Ave. Azusa, CA 91702 -Original Message- From: Hilco Wijbenga [mailto:hilco.wijbe...@gmail.com] Sent: Monday, January 31, 2011 1:19 PM To: Maven Users List Subject: Re: Error building simple web project On 31 January 2011 13:08, Kenneth Litwak klit...@apu.edu wrote: I'm writing a web app with Maven and learning as I go. The packaging is war. I have a directory within my project that has the web pieces: web src main webapp WEB-INF Web.xml Is this just a copy-and-paste thing or did you really name it Web.xml? It should be web.xml (all lowercase). - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Regarding Automating Deployment to JBoss from Nexus
Currently I am able to build my artifacts using Maven and successfully published to Nexus repository. I want to deploy deploy the war files and other configuration zip files from Nexus to the remote Jboss server. I have few doubts regarding this. You would probably benefit from installing a CI server like Hudson/Jenkins to use for this purpose. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Error building simple web project
n Mon, Jan 31, 2011 at 5:20 PM, Kenneth Litwak klit...@apu.edu wrote: Sorry, just a copy-and-paste error. I know the real thing has to have all lower-case. WEB-INF/web.xml -- I haven't seen that error before. Maybe the web.xml isn't correctly formed? Greg Akins http://twitter.com/akinsgre
RE: Error building simple web project
I resolved this error. I didn't realize how complex the structure of a web app was in Maven. Now that I added that complexity and have POMs all over the place, the project builds. Thanks. Kenneth D. Litwak, Ph.D. Azusa Pacific University 901 E. Alosta Ave. Azusa, CA 91702 -Original Message- From: Greg Akins [mailto:angryg...@gmail.com] Sent: Monday, January 31, 2011 3:54 PM To: Maven Users List Subject: Re: Error building simple web project n Mon, Jan 31, 2011 at 5:20 PM, Kenneth Litwak klit...@apu.edu wrote: Sorry, just a copy-and-paste error. I know the real thing has to have all lower-case. WEB-INF/web.xml -- I haven't seen that error before. Maybe the web.xml isn't correctly formed? Greg Akins http://twitter.com/akinsgre - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
