Re: maven doesn't filter dependencies defined in pom
property substitution is not supported in
/project(/parent)?/version
2009/10/29 Pepe Perez pp.pe...@yahoo.com
Hello,
This is the situation I'm in.
I have this structure
pom.xml (root)
|_ pom.xml (module A)
|_ pom.xml (module B)
These are (excerpts) of the poms
pom.xml (root)
groupIdrootGroupId/groupId
artifactIdrootArtifactId/artifactId
packagingpom/packaging
version${rootGroupId}/version
modules
modulemoduleA/module
modulemoduleB/module
/modules
properties
moduleAGroupId1.0-SNAPSHOT/moduleAGroupId
moduleBGroupId1.0-SNAPSHOT/moduleBGroupId
rootGroupIdrootVersion/rootGroupId
/properties
pom (module A)
parent
groupIdrootGroupId/groupId
artifactIdrootArtifactId/artifactId
version${rootGroupId}/version
/parent
groupIdmoduleAGroupId/groupId
artifactIdmoduleAArtifactId/artifactId
packagingpom/packaging
version${moduleAGroupId}/version
pom (module B)
parent
groupIdrootGroupId/groupId
artifactIdrootArtifactId/artifactId
version${rootGroupId}/version
/parent
groupIdmoduleBGroupId/groupId
artifactIdmoduleBArtifactId/artifactId
packagingpom/packaging
version${moduleBGroupId}/version
dependencies
dependency
groupIdmoduleAGroupId/groupId
artifactIdmoduleAArtifactId/artifactId
version${moduleAGroupId}/version
dependency
/dependency
cd root
mvn install
[INFO] BUILD SUCCESSFUL
[INFO]
cd moduleB
mvn install
[WARNING] Unable to get resource
'moduleAGroupId:moduleAArtifactId:${moduleAGroupId}'
from repository central (http://repo1.maven.org/maven2): Error
transferring file: Server returned HTTP response code: 500 for URL:
http://pom_maven_repo_location
[ERROR] BUILD ERROR
[INFO]
[INFO] Error building POM (may not be this project's POM).
Project ID: moduleB
Reason: Cannot find parent: moduleA pom for project: moduleB
This is happening because when building moduleA its pom file is
installed in the maven repo without filtering, i.e, as it is with ${}.
When the pom is retrieved to satisfy moduleB dependency on moduleA it's
retrieved as
groupIdmoduleAGroupId/groupId
artifactIdmoduleAArtifactId/artifactId
packagingpom/packaging
version${moduleAGroupId}/version
where ${moduleAGroupId} is not instanciated, hence the error.
My question is:
1. Could I force maven to store the pom files **filtered** or
2. How can maven be forced to instantiate ${moduleAGroupId} upon
retrieval from the maven repo so moduleB dependency can be satisfied
3. What other alternative do I have to solve this scenario without
giving up using ${} in version
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: maven doesn't filter dependencies defined in pom
2009/10/29 Stephen Connolly stephen.alan.conno...@gmail.com
property substitution is not supported in
/project(/parent)?/version
2009/10/29 Pepe Perez pp.pe...@yahoo.com
Hello,
This is the situation I'm in.
I have this structure
pom.xml (root)
|_ pom.xml (module A)
|_ pom.xml (module B)
These are (excerpts) of the poms
pom.xml (root)
groupIdrootGroupId/groupId
artifactIdrootArtifactId/artifactId
packagingpom/packaging
version${rootGroupId}/version
modules
modulemoduleA/module
modulemoduleB/module
/modules
properties
moduleAGroupId1.0-SNAPSHOT/moduleAGroupId
moduleBGroupId1.0-SNAPSHOT/moduleBGroupId
rootGroupIdrootVersion/rootGroupId
/properties
pom (module A)
parent
groupIdrootGroupId/groupId
artifactIdrootArtifactId/artifactId
version${rootGroupId}/version
/parent
because maven does not know rootGroupId until it fetches the parent, it does
not know what parent to fetch, so it does not know moduleAGroupId either
groupIdmoduleAGroupId/groupId
artifactIdmoduleAArtifactId/artifactId
packagingpom/packaging
version${moduleAGroupId}/version
pom (module B)
parent
groupIdrootGroupId/groupId
artifactIdrootArtifactId/artifactId
version${rootGroupId}/version
/parent
groupIdmoduleBGroupId/groupId
artifactIdmoduleBArtifactId/artifactId
packagingpom/packaging
version${moduleBGroupId}/version
dependencies
dependency
groupIdmoduleAGroupId/groupId
artifactIdmoduleAArtifactId/artifactId
version${moduleAGroupId}/version
dependency
/dependency
cd root
mvn install
[INFO] BUILD SUCCESSFUL
[INFO]
cd moduleB
mvn install
[WARNING] Unable to get resource
'moduleAGroupId:moduleAArtifactId:${moduleAGroupId}'
from repository central (http://repo1.maven.org/maven2): Error
transferring file: Server returned HTTP response code: 500 for URL:
http://pom_maven_repo_location
[ERROR] BUILD ERROR
[INFO]
[INFO] Error building POM (may not be this project's POM).
Project ID: moduleB
Reason: Cannot find parent: moduleA pom for project: moduleB
This is happening because when building moduleA its pom file is
installed in the maven repo without filtering, i.e, as it is with ${}.
When the pom is retrieved to satisfy moduleB dependency on moduleA it's
retrieved as
groupIdmoduleAGroupId/groupId
artifactIdmoduleAArtifactId/artifactId
packagingpom/packaging
version${moduleAGroupId}/version
where ${moduleAGroupId} is not instanciated, hence the error.
My question is:
1. Could I force maven to store the pom files **filtered** or
2. How can maven be forced to instantiate ${moduleAGroupId} upon
retrieval from the maven repo so moduleB dependency can be satisfied
3. What other alternative do I have to solve this scenario without
giving up using ${} in version
why do you need to use properties for /project(/parent)?/version
if you use the release plugin, it will update those correctly, and as well
will likely update the dependencies for you. It would seem to me that your
use case would be better served with a dependencyManagement section in the
root pom. then you can omit the version in the dependency sections of each
child pom such that the only versions specified are
in /project(/parent)?/version
Also, if you are going to release all of them in the same go, you should
note that /project/version is inherited from /project/parent/version
my solution would be as follows:
pom.xml (root)
project
groupIdrootGroupId/groupId
artifactIdrootArtifactId/artifactId
packagingpom/packaging
version1.0-SNAPSHOT/version
modules
modulemoduleA/module
modulemoduleB/module
/modules
dependencyManagement
dependencies
dependency
groupIdmoduleAGroupId/groupId
artifactIdmoduleAArtifactId/artifactId
version1.0-SNAPSHOT/version
/dependency
/dependencies
/dependencyManagement
/project
pom.xml (module A)
project
parent
groupIdrootGroupId/groupId
artifactIdrootArtifactId/artifactId
version1.0-SNAPSHOT/version
/parent
groupIdmoduleAGroupId/groupId
artifactIdmoduleAArtifactId/artifactId
/project
pom.xml (module B)
project
parent
groupIdrootGroupId/groupId
artifactIdrootArtifactId/artifactId
version1.0-SNAPSHOT/version
/parent
groupIdmoduleBGroupId/groupId
artifactIdmoduleBArtifactId/artifactId
dependencies
dependency
groupIdmoduleAGroupId/groupId
artifactIdmoduleAArtifactId/artifactId
version1.0-SNAPSHOT/version
/dependency
Re: Selectively include and exclude class file while building the artifact
specify includes/excludes relative to the path in the jar. 2009/10/29 anil.kumar anilkumar7...@gmail.com Requirement: In initial stage I will compile all the files coming under my project source directory. Finally at the time of making the jar I need to selectively include and exclude certain files. The files which are to be included and excluded comes under my project source directory. My Project source directory : F:/ARL/HIS/src/ I am able to successfully compile all the files coming under my source directory. It is being saved in the location : F:/ARL/HIS/src/classes/ Sample code to include and exclude class files to make the jar file. plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId executions execution phasepackage/phase goals goaljar/goal /goals configuration classifierclient/classifier excludes exclude F:\ARL\HIS\src\classes\*.class/exclude// added for testing purpose to check if exclude tags work or not /excludes /configuration /execution /executions /plugin While executing the goal mvn org.apache.maven.plugins:maven-jar-plugin:jar , for making the jar file it takes all the files coming under classes directory where as i have specifically mentioned it not to be included while making the jar file. Where am I going wrong ? -- View this message in context: http://www.nabble.com/Selectively-include-and-exclude-class-file-while-building-the-artifact-tp26107145p26107145.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: maven doesn't filter dependencies defined in pom
Stephen,
I think it is... to some extent at least
Both moduleA and moduleB have this parent block
parent
groupIdrootGroupId/groupId
artifactIdrootArtifactId/artifactId
version${rootGroupId}/version
/parent
That following property rootGroupIdrootVersion/rootGroupId is correctly
parsed into
parent
groupIdrootGroupId/groupId
artifactIdrootArtifactId/artifactId
versionrootVersion/version
/parent
which makes the build be successful if started from the root.
- Original Message
From: Stephen Connolly stephen.alan.conno...@gmail.com
To: Maven Users List users@maven.apache.org
Sent: Wed, October 28, 2009 11:19:17 PM
Subject: Re: maven doesn't filter dependencies defined in pom
property substitution is not supported in
/project(/parent)?/version
2009/10/29 Pepe Perez pp.pe...@yahoo.com
Hello,
This is the situation I'm in.
I have this structure
pom.xml (root)
|_ pom.xml (module A)
|_ pom.xml (module B)
These are (excerpts) of the poms
pom.xml (root)
groupIdrootGroupId/groupId
artifactIdrootArtifactId/artifactId
packagingpom/packaging
version${rootGroupId}/version
modules
modulemoduleA/module
modulemoduleB/module
/modules
properties
moduleAGroupId1.0-SNAPSHOT/moduleAGroupId
moduleBGroupId1.0-SNAPSHOT/moduleBGroupId
rootGroupIdrootVersion/rootGroupId
/properties
pom (module A)
parent
groupIdrootGroupId/groupId
artifactIdrootArtifactId/artifactId
version${rootGroupId}/version
/parent
groupIdmoduleAGroupId/groupId
artifactIdmoduleAArtifactId/artifactId
packagingpom/packaging
version${moduleAGroupId}/version
pom (module B)
parent
groupIdrootGroupId/groupId
artifactIdrootArtifactId/artifactId
version${rootGroupId}/version
/parent
groupIdmoduleBGroupId/groupId
artifactIdmoduleBArtifactId/artifactId
packagingpom/packaging
version${moduleBGroupId}/version
dependencies
dependency
groupIdmoduleAGroupId/groupId
artifactIdmoduleAArtifactId/artifactId
version${moduleAGroupId}/version
dependency
/dependency
cd root
mvn install
[INFO] BUILD SUCCESSFUL
[INFO]
cd moduleB
mvn install
[WARNING] Unable to get resource
'moduleAGroupId:moduleAArtifactId:${moduleAGroupId}'
from repository central (http://repo1.maven.org/maven2): Error
transferring file: Server returned HTTP response code: 500 for URL:
http://pom_maven_repo_location
[ERROR] BUILD ERROR
[INFO]
[INFO] Error building POM (may not be this project's POM).
Project ID: moduleB
Reason: Cannot find parent: moduleA pom for project: moduleB
This is happening because when building moduleA its pom file is
installed in the maven repo without filtering, i.e, as it is with ${}.
When the pom is retrieved to satisfy moduleB dependency on moduleA it's
retrieved as
groupIdmoduleAGroupId/groupId
artifactIdmoduleAArtifactId/artifactId
packagingpom/packaging
version${moduleAGroupId}/version
where ${moduleAGroupId} is not instanciated, hence the error.
My question is:
1. Could I force maven to store the pom files **filtered** or
2. How can maven be forced to instantiate ${moduleAGroupId} upon
retrieval from the maven repo so moduleB dependency can be satisfied
3. What other alternative do I have to solve this scenario without
giving up using ${} in version
-
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: maven doesn't filter dependencies defined in pom
2009/10/29 Pepe Perez pp.pe...@yahoo.com
Stephen,
I think it is... to some extent at least
Both moduleA and moduleB have this parent block
parent
groupIdrootGroupId/groupId
artifactIdrootArtifactId/artifactId
version${rootGroupId}/version
/parent
That following property rootGroupIdrootVersion/rootGroupId is correctly
parsed into
actually that property is not parsed when building from the root...
(short answer, there is a more long and technical answer which you are not
interested in) ;-)
parent
groupIdrootGroupId/groupId
artifactIdrootArtifactId/artifactId
versionrootVersion/version
/parent
which makes the build be successful if started from the root.
- Original Message
From: Stephen Connolly stephen.alan.conno...@gmail.com
To: Maven Users List users@maven.apache.org
Sent: Wed, October 28, 2009 11:19:17 PM
Subject: Re: maven doesn't filter dependencies defined in pom
property substitution is not supported in
/project(/parent)?/version
2009/10/29 Pepe Perez pp.pe...@yahoo.com
Hello,
This is the situation I'm in.
I have this structure
pom.xml (root)
|_ pom.xml (module A)
|_ pom.xml (module B)
These are (excerpts) of the poms
pom.xml (root)
groupIdrootGroupId/groupId
artifactIdrootArtifactId/artifactId
packagingpom/packaging
version${rootGroupId}/version
modules
modulemoduleA/module
modulemoduleB/module
/modules
properties
moduleAGroupId1.0-SNAPSHOT/moduleAGroupId
moduleBGroupId1.0-SNAPSHOT/moduleBGroupId
rootGroupIdrootVersion/rootGroupId
/properties
pom (module A)
parent
groupIdrootGroupId/groupId
artifactIdrootArtifactId/artifactId
version${rootGroupId}/version
/parent
groupIdmoduleAGroupId/groupId
artifactIdmoduleAArtifactId/artifactId
packagingpom/packaging
version${moduleAGroupId}/version
pom (module B)
parent
groupIdrootGroupId/groupId
artifactIdrootArtifactId/artifactId
version${rootGroupId}/version
/parent
groupIdmoduleBGroupId/groupId
artifactIdmoduleBArtifactId/artifactId
packagingpom/packaging
version${moduleBGroupId}/version
dependencies
dependency
groupIdmoduleAGroupId/groupId
artifactIdmoduleAArtifactId/artifactId
version${moduleAGroupId}/version
dependency
/dependency
cd root
mvn install
[INFO] BUILD SUCCESSFUL
[INFO]
cd moduleB
mvn install
[WARNING] Unable to get resource
'moduleAGroupId:moduleAArtifactId:${moduleAGroupId}'
from repository central (http://repo1.maven.org/maven2): Error
transferring file: Server returned HTTP response code: 500 for URL:
http://pom_maven_repo_location
[ERROR] BUILD ERROR
[INFO]
[INFO] Error building POM (may not be this project's POM).
Project ID: moduleB
Reason: Cannot find parent: moduleA pom for project: moduleB
This is happening because when building moduleA its pom file is
installed in the maven repo without filtering, i.e, as it is with ${}.
When the pom is retrieved to satisfy moduleB dependency on moduleA it's
retrieved as
groupIdmoduleAGroupId/groupId
artifactIdmoduleAArtifactId/artifactId
packagingpom/packaging
version${moduleAGroupId}/version
where ${moduleAGroupId} is not instanciated, hence the error.
My question is:
1. Could I force maven to store the pom files **filtered** or
2. How can maven be forced to instantiate ${moduleAGroupId} upon
retrieval from the maven repo so moduleB dependency can be satisfied
3. What other alternative do I have to solve this scenario without
giving up using ${} in version
-
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: maven doesn't filter dependencies defined in pom
using dependencyManagement would solve my problem for the dependencies, but due
to my project requirements I still need to use a property in the parent
version, which is not managed by dependencyManagement.
From what I can see maven doesn't have any problem in replacing properties in
the parent block of the current pom, but it does when it retrieves the pom
of a dependency from the repo to which it was previously downloaded when
building from the root. This pom taken from the repo has a property in the
parent section, and contrary to what maven does for the current pom maven
doesn't replace properties here.
My issue would be solve if the poms where installed into the maven repo with
the properties already replaced by their value, or if it replaced properties in
the poms retrieved from the repo to calculate transitive dependencies.
- Original Message
From: Stephen Connolly stephen.alan.conno...@gmail.com
To: Maven Users List users@maven.apache.org
Sent: Wed, October 28, 2009 11:30:37 PM
Subject: Re: maven doesn't filter dependencies defined in pom
2009/10/29 Stephen Connolly stephen.alan.conno...@gmail.com
property substitution is not supported in
/project(/parent)?/version
2009/10/29 Pepe Perez pp.pe...@yahoo.com
Hello,
This is the situation I'm in.
I have this structure
pom.xml (root)
|_ pom.xml (module A)
|_ pom.xml (module B)
These are (excerpts) of the poms
pom.xml (root)
groupIdrootGroupId/groupId
artifactIdrootArtifactId/artifactId
packagingpom/packaging
version${rootGroupId}/version
modules
modulemoduleA/module
modulemoduleB/module
/modules
properties
moduleAGroupId1.0-SNAPSHOT/moduleAGroupId
moduleBGroupId1.0-SNAPSHOT/moduleBGroupId
rootGroupIdrootVersion/rootGroupId
/properties
pom (module A)
parent
groupIdrootGroupId/groupId
artifactIdrootArtifactId/artifactId
version${rootGroupId}/version
/parent
because maven does not know rootGroupId until it fetches the parent, it does
not know what parent to fetch, so it does not know moduleAGroupId either
groupIdmoduleAGroupId/groupId
artifactIdmoduleAArtifactId/artifactId
packagingpom/packaging
version${moduleAGroupId}/version
pom (module B)
parent
groupIdrootGroupId/groupId
artifactIdrootArtifactId/artifactId
version${rootGroupId}/version
/parent
groupIdmoduleBGroupId/groupId
artifactIdmoduleBArtifactId/artifactId
packagingpom/packaging
version${moduleBGroupId}/version
dependencies
dependency
groupIdmoduleAGroupId/groupId
artifactIdmoduleAArtifactId/artifactId
version${moduleAGroupId}/version
dependency
/dependency
cd root
mvn install
[INFO] BUILD SUCCESSFUL
[INFO]
cd moduleB
mvn install
[WARNING] Unable to get resource
'moduleAGroupId:moduleAArtifactId:${moduleAGroupId}'
from repository central (http://repo1.maven.org/maven2): Error
transferring file: Server returned HTTP response code: 500 for URL:
http://pom_maven_repo_location
[ERROR] BUILD ERROR
[INFO]
[INFO] Error building POM (may not be this project's POM).
Project ID: moduleB
Reason: Cannot find parent: moduleA pom for project: moduleB
This is happening because when building moduleA its pom file is
installed in the maven repo without filtering, i.e, as it is with ${}.
When the pom is retrieved to satisfy moduleB dependency on moduleA it's
retrieved as
groupIdmoduleAGroupId/groupId
artifactIdmoduleAArtifactId/artifactId
packagingpom/packaging
version${moduleAGroupId}/version
where ${moduleAGroupId} is not instanciated, hence the error.
My question is:
1. Could I force maven to store the pom files **filtered** or
2. How can maven be forced to instantiate ${moduleAGroupId} upon
retrieval from the maven repo so moduleB dependency can be satisfied
3. What other alternative do I have to solve this scenario without
giving up using ${} in version
why do you need to use properties for /project(/parent)?/version
if you use the release plugin, it will update those correctly, and as well
will likely update the dependencies for you. It would seem to me that your
use case would be better served with a dependencyManagement section in the
root pom. then you can omit the version in the dependency sections of each
child pom such that the only versions specified are
in /project(/parent)?/version
Also, if you are going to release all of them in the same go, you should
note that /project/version is inherited from /project/parent/version
my solution would be as follows:
pom.xml (root)
project
groupIdrootGroupId/groupId
Re: AW: resouce files not in the built jar
I do use m2eclipse to build my project and then use clean package to compile
it.
Now I move the context.xml to /src/main/resources and I can find it in
jar.
But as I start to run the program in Eclipse I got exception like:
[code]
...
Exception in thread main
org.springframework.beans.factory.BeanDefinitionStoreException: IOException
parsing XML document from class path resource [context.xml]; nested
exception is java.io.FileNotFoundException: class path resource
[context.xml] cannot be opened because it does not exist
...
[/code]
My class looks like:
[code]
...
public class App {
public static void main(String[] args) {
ApplicationContext context = new
ClassPathXmlApplicationContext(context.xml, TestBean.class);
TestBean testBean = (TestBean) context.getBean(test);
}
}
[/code]
And here is my POM.XML
[code]
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/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdcom.weichen.app/groupId
artifactIdTestSimpleStandAloneSpringApp/artifactId
packagingjar/packaging
version1.0/version
nameTestSimpleStandAloneSpringApp/name
urlhttp://maven.apache.org/url
properties
spring.version2.5.4/spring.version
/properties
dependencies
dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version3.8.1/version
scopetest/scope
/dependency
dependency
groupIdorg.springframework/groupId
artifactIdspring/artifactId
version${spring.version}/version
/dependency
/dependencies
build
sourceDirectorysrc/main/java/sourceDirectory
resources
resource
directorysrc/main/resources/directory
/resource
/resources
pluginManagement
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
source1.5/source
target1.5/target
/configuration
/plugin
/plugins
/pluginManagement
/build
/project
[/code]
Lewis, Eric wrote:
Also, if you're not yet using it, get m2eclipse and import your Maven
project.
src/main/resources will be treated as source folder automatically.
Best regards,
Eric
-Ursprüngliche Nachricht-
Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Gesendet: Mittwoch, 28. Oktober 2009 15:27
An: Maven Users List
Betreff: Re: resouce files not in the built jar
because resources should be in src/main/resources/___ and not
src/main/java/___
eclipse is a fool... maven is a know-all
-Stephen
2009/10/28 thomas2004 thomas200...@yahoo.de
Hi all,
I use maven 2.0.9 and Eclipse to build my program. But I met a strange
thing: I put some resource files such as context.xml in the same
package
as my java files. But after I built the project/program with mvn clean
package, I can't find the context.xml inside the jar. That's the reason
why I got FileNotFoundException as I run the program.
Someone knows why?
--
View this message in context:
http://www.nabble.com/resouce-files-not-in-the-built-jar-tp26095189p26095189.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
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
View this message in context:
http://www.nabble.com/resouce-files-not-in-the-built-jar-tp26095189p26107811.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: Selectively include and exclude class file while building the artifact
Anil, Please reply to the list so that others may find the solutions to the problem (i.e. let google be their friend) To answer your question: Nope... I said the path *_in the jar_* so to exclude the class com.foo.bar.Manchu you would use excludecom/foo/bar/Manchu.class/exclude to exclude the entire com.foo.bar package you would use excludecom/foo/bar/**/exclude and to exclude all the dto packages you would use something like exclude**/dto/**/exclude -Stephen 2009/10/29 anilkumar7...@gmail.com So in my case as the jar and compiled class files are being stored in directory F:/ARL/HIS/src/target/ and F:/ARL/HIS/src/classes/ , the relative to the class files will be F:/ARL/HIS/src/target/../classes/ . In this case the jar file created should be empty but it includes all the class files coming under classes directory. Regards, Anil Stephen Connolly-2 wrote: specify includes/excludes relative to the path in the jar. 2009/10/29 anil.kumar anilkumar7...@gmail.com Requirement: In initial stage I will compile all the files coming under my project source directory. Finally at the time of making the jar I need to selectively include and exclude certain files. The files which are to be included and excluded comes under my project source directory. My Project source directory : F:/ARL/HIS/src/ I am able to successfully compile all the files coming under my source directory. It is being saved in the location : F:/ARL/HIS/src/classes/ Sample code to include and exclude class files to make the jar file. plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId executions execution phasepackage/phase goals goaljar/goal /goals configuration classifierclient/classifier excludes exclude F:\ARL\HIS\src\classes\*.class/exclude// added for testing purpose to check if exclude tags work or not /excludes /configuration /execution /executions /plugin While executing the goal mvn org.apache.maven.plugins:maven-jar-plugin:jar , for making the jar file it takes all the files coming under classes directory where as i have specifically mentioned it not to be included while making the jar file. Where am I going wrong ? -- View this message in context: http://www.nabble.com/Selectively-include-and-exclude-class-file-while-building-the-artifact-tp26107145p26107145.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 Quoted from: http://www.nabble.com/Selectively-include-and-exclude-class-file-while-building-the-artifact-tp26107145p26107471.html
Re: Selectively include and exclude class file while building the artifact
Stephen, I thought by emailing is the only way you will be notified when I reply to the topic unless you sub scribe to the thread. Hence forth I will only post my queries in the forum. Thanks for letting me know. Coming to the topic ,it didn't work out. I will give this a try once more else I may have to look for other possible alternatives like maven-assembly-plugin. Thanks for your time. Stephen Connolly-2 wrote: Anil, Please reply to the list so that others may find the solutions to the problem (i.e. let google be their friend) To answer your question: Nope... I said the path *_in the jar_* so to exclude the class com.foo.bar.Manchu you would use excludecom/foo/bar/Manchu.class/exclude to exclude the entire com.foo.bar package you would use excludecom/foo/bar/**/exclude and to exclude all the dto packages you would use something like exclude**/dto/**/exclude -Stephen 2009/10/29 anilkumar7...@gmail.com So in my case as the jar and compiled class files are being stored in directory F:/ARL/HIS/src/target/ and F:/ARL/HIS/src/classes/ , the relative to the class files will be F:/ARL/HIS/src/target/../classes/ . In this case the jar file created should be empty but it includes all the class files coming under classes directory. Regards, Anil Stephen Connolly-2 wrote: specify includes/excludes relative to the path in the jar. 2009/10/29 anil.kumar anilkumar7...@gmail.com Requirement: In initial stage I will compile all the files coming under my project source directory. Finally at the time of making the jar I need to selectively include and exclude certain files. The files which are to be included and excluded comes under my project source directory. My Project source directory : F:/ARL/HIS/src/ I am able to successfully compile all the files coming under my source directory. It is being saved in the location : F:/ARL/HIS/src/classes/ Sample code to include and exclude class files to make the jar file. plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId executions execution phasepackage/phase goals goaljar/goal /goals configuration classifierclient/classifier excludes exclude F:\ARL\HIS\src\classes\*.class/exclude// added for testing purpose to check if exclude tags work or not /excludes /configuration /execution /executions /plugin While executing the goal mvn org.apache.maven.plugins:maven-jar-plugin:jar , for making the jar file it takes all the files coming under classes directory where as i have specifically mentioned it not to be included while making the jar file. Where am I going wrong ? -- View this message in context: http://www.nabble.com/Selectively-include-and-exclude-class-file-while-building-the-artifact-tp26107145p26107145.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 Quoted from: http://www.nabble.com/Selectively-include-and-exclude-class-file-while-building-the-artifact-tp26107145p26107471.html -- View this message in context: http://www.nabble.com/Selectively-include-and-exclude-class-file-while-building-the-artifact-tp26107145p26109882.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: proper NAR locations
Hi Damon, On Oct 28, 2009, at 10:35 PM, Damon Jacobsen wrote: I have switched to trying to use the MinGW compiler instead of Borland. ok. I have it working for the most part now. I am curious on proper locations of files. I am compiling a jni component that links to a third party library for a dll Should the lib and dll be in the jni maven project, or placed in another project? yes, they should be as the jni part will not work without the library/ dll. What is the proper directory structure for these artifacts? look into src/it for some test with 3rd party lib. Will the dll be moved out with the jni dll when loadLibrary is called? the lib and dll will be in nar file. loadLibrary knows nothing about nar, so some kind of installation/assembly (and I am not sure we have that currently) needs to be done in the final deployment. Do I need to explicitly add the lib file in the linker configuration of the pom, or will the nar plugin find it once it is in the correct location? When you declare a nar project, you only depend on jar type dependencies. nar file will be found, downloaded and unpacked for usage. If you create a jar/normal project, then some unpacking needs to be done. Again I am not sure we have that yet. Sorry, I left the project dangling 2 years ago, for a different job. Got back into it a month ago, but have not looked at everything yet. Regards Mark Damon Jacobsen __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email _ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Selectively include and exclude class file while building the artifact
you might require a leading / 2009/10/29 anil.kumar anilkumar7...@gmail.com Stephen, I thought by emailing is the only way you will be notified when I reply to the topic unless you sub scribe to the thread. Hence forth I will only post my queries in the forum. Thanks for letting me know. Coming to the topic ,it didn't work out. I will give this a try once more else I may have to look for other possible alternatives like maven-assembly-plugin. Thanks for your time. Stephen Connolly-2 wrote: Anil, Please reply to the list so that others may find the solutions to the problem (i.e. let google be their friend) To answer your question: Nope... I said the path *_in the jar_* so to exclude the class com.foo.bar.Manchu you would use excludecom/foo/bar/Manchu.class/exclude to exclude the entire com.foo.bar package you would use excludecom/foo/bar/**/exclude and to exclude all the dto packages you would use something like exclude**/dto/**/exclude -Stephen 2009/10/29 anilkumar7...@gmail.com So in my case as the jar and compiled class files are being stored in directory F:/ARL/HIS/src/target/ and F:/ARL/HIS/src/classes/ , the relative to the class files will be F:/ARL/HIS/src/target/../classes/ . In this case the jar file created should be empty but it includes all the class files coming under classes directory. Regards, Anil Stephen Connolly-2 wrote: specify includes/excludes relative to the path in the jar. 2009/10/29 anil.kumar anilkumar7...@gmail.com Requirement: In initial stage I will compile all the files coming under my project source directory. Finally at the time of making the jar I need to selectively include and exclude certain files. The files which are to be included and excluded comes under my project source directory. My Project source directory : F:/ARL/HIS/src/ I am able to successfully compile all the files coming under my source directory. It is being saved in the location : F:/ARL/HIS/src/classes/ Sample code to include and exclude class files to make the jar file. plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId executions execution phasepackage/phase goals goaljar/goal /goals configuration classifierclient/classifier excludes exclude F:\ARL\HIS\src\classes\*.class/exclude// added for testing purpose to check if exclude tags work or not /excludes /configuration /execution /executions /plugin While executing the goal mvn org.apache.maven.plugins:maven-jar-plugin:jar , for making the jar file it takes all the files coming under classes directory where as i have specifically mentioned it not to be included while making the jar file. Where am I going wrong ? -- View this message in context: http://www.nabble.com/Selectively-include-and-exclude-class-file-while-building-the-artifact-tp26107145p26107145.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 Quoted from: http://www.nabble.com/Selectively-include-and-exclude-class-file-while-building-the-artifact-tp26107145p26107471.html -- View this message in context: http://www.nabble.com/Selectively-include-and-exclude-class-file-while-building-the-artifact-tp26107145p26109882.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: Selectively include and exclude class file while building the artifact
Tried this as well. Not working. Stephen Connolly-2 wrote: you might require a leading / 2009/10/29 anil.kumar anilkumar7...@gmail.com Stephen, I thought by emailing is the only way you will be notified when I reply to the topic unless you sub scribe to the thread. Hence forth I will only post my queries in the forum. Thanks for letting me know. Coming to the topic ,it didn't work out. I will give this a try once more else I may have to look for other possible alternatives like maven-assembly-plugin. Thanks for your time. Stephen Connolly-2 wrote: Anil, Please reply to the list so that others may find the solutions to the problem (i.e. let google be their friend) To answer your question: Nope... I said the path *_in the jar_* so to exclude the class com.foo.bar.Manchu you would use excludecom/foo/bar/Manchu.class/exclude to exclude the entire com.foo.bar package you would use excludecom/foo/bar/**/exclude and to exclude all the dto packages you would use something like exclude**/dto/**/exclude -Stephen 2009/10/29 anilkumar7...@gmail.com So in my case as the jar and compiled class files are being stored in directory F:/ARL/HIS/src/target/ and F:/ARL/HIS/src/classes/ , the relative to the class files will be F:/ARL/HIS/src/target/../classes/ . In this case the jar file created should be empty but it includes all the class files coming under classes directory. Regards, Anil Stephen Connolly-2 wrote: specify includes/excludes relative to the path in the jar. 2009/10/29 anil.kumar anilkumar7...@gmail.com Requirement: In initial stage I will compile all the files coming under my project source directory. Finally at the time of making the jar I need to selectively include and exclude certain files. The files which are to be included and excluded comes under my project source directory. My Project source directory : F:/ARL/HIS/src/ I am able to successfully compile all the files coming under my source directory. It is being saved in the location : F:/ARL/HIS/src/classes/ Sample code to include and exclude class files to make the jar file. plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId executions execution phasepackage/phase goals goaljar/goal /goals configuration classifierclient/classifier excludes exclude F:\ARL\HIS\src\classes\*.class/exclude// added for testing purpose to check if exclude tags work or not /excludes /configuration /execution /executions /plugin While executing the goal mvn org.apache.maven.plugins:maven-jar-plugin:jar , for making the jar file it takes all the files coming under classes directory where as i have specifically mentioned it not to be included while making the jar file. Where am I going wrong ? -- View this message in context: http://www.nabble.com/Selectively-include-and-exclude-class-file-while-building-the-artifact-tp26107145p26107145.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 Quoted from: http://www.nabble.com/Selectively-include-and-exclude-class-file-while-building-the-artifact-tp26107145p26107471.html -- View this message in context: http://www.nabble.com/Selectively-include-and-exclude-class-file-while-building-the-artifact-tp26107145p26109882.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 -- View this message in context: http://www.nabble.com/Selectively-include-and-exclude-class-file-while-building-the-artifact-tp26107145p26110534.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: Selectively include and exclude class file while building the artifact
well just clobber it with a **/ as the prefix ;-) 2009/10/29 anil.kumar anilkumar7...@gmail.com Tried this as well. Not working. Stephen Connolly-2 wrote: you might require a leading / 2009/10/29 anil.kumar anilkumar7...@gmail.com Stephen, I thought by emailing is the only way you will be notified when I reply to the topic unless you sub scribe to the thread. Hence forth I will only post my queries in the forum. Thanks for letting me know. Coming to the topic ,it didn't work out. I will give this a try once more else I may have to look for other possible alternatives like maven-assembly-plugin. Thanks for your time. Stephen Connolly-2 wrote: Anil, Please reply to the list so that others may find the solutions to the problem (i.e. let google be their friend) To answer your question: Nope... I said the path *_in the jar_* so to exclude the class com.foo.bar.Manchu you would use excludecom/foo/bar/Manchu.class/exclude to exclude the entire com.foo.bar package you would use excludecom/foo/bar/**/exclude and to exclude all the dto packages you would use something like exclude**/dto/**/exclude -Stephen 2009/10/29 anilkumar7...@gmail.com So in my case as the jar and compiled class files are being stored in directory F:/ARL/HIS/src/target/ and F:/ARL/HIS/src/classes/ , the relative to the class files will be F:/ARL/HIS/src/target/../classes/ . In this case the jar file created should be empty but it includes all the class files coming under classes directory. Regards, Anil Stephen Connolly-2 wrote: specify includes/excludes relative to the path in the jar. 2009/10/29 anil.kumar anilkumar7...@gmail.com Requirement: In initial stage I will compile all the files coming under my project source directory. Finally at the time of making the jar I need to selectively include and exclude certain files. The files which are to be included and excluded comes under my project source directory. My Project source directory : F:/ARL/HIS/src/ I am able to successfully compile all the files coming under my source directory. It is being saved in the location : F:/ARL/HIS/src/classes/ Sample code to include and exclude class files to make the jar file. plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId executions execution phasepackage/phase goals goaljar/goal /goals configuration classifierclient/classifier excludes exclude F:\ARL\HIS\src\classes\*.class/exclude// added for testing purpose to check if exclude tags work or not /excludes /configuration /execution /executions /plugin While executing the goal mvn org.apache.maven.plugins:maven-jar-plugin:jar , for making the jar file it takes all the files coming under classes directory where as i have specifically mentioned it not to be included while making the jar file. Where am I going wrong ? -- View this message in context: http://www.nabble.com/Selectively-include-and-exclude-class-file-while-building-the-artifact-tp26107145p26107145.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 Quoted from: http://www.nabble.com/Selectively-include-and-exclude-class-file-while-building-the-artifact-tp26107145p26107471.html -- View this message in context: http://www.nabble.com/Selectively-include-and-exclude-class-file-while-building-the-artifact-tp26107145p26109882.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 -- View this message in context: http://www.nabble.com/Selectively-include-and-exclude-class-file-while-building-the-artifact-tp26107145p26110534.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: Selectively include and exclude class file while building the artifact
Wanted to know one thing .Is the issue related to the way I have named the path to be mentioned in exclude tag. I have tried out all possible combination's . Still not working. Stephen Connolly-2 wrote: well just clobber it with a **/ as the prefix ;-) 2009/10/29 anil.kumar anilkumar7...@gmail.com Tried this as well. Not working. Stephen Connolly-2 wrote: you might require a leading / 2009/10/29 anil.kumar anilkumar7...@gmail.com Stephen, I thought by emailing is the only way you will be notified when I reply to the topic unless you sub scribe to the thread. Hence forth I will only post my queries in the forum. Thanks for letting me know. Coming to the topic ,it didn't work out. I will give this a try once more else I may have to look for other possible alternatives like maven-assembly-plugin. Thanks for your time. Stephen Connolly-2 wrote: Anil, Please reply to the list so that others may find the solutions to the problem (i.e. let google be their friend) To answer your question: Nope... I said the path *_in the jar_* so to exclude the class com.foo.bar.Manchu you would use excludecom/foo/bar/Manchu.class/exclude to exclude the entire com.foo.bar package you would use excludecom/foo/bar/**/exclude and to exclude all the dto packages you would use something like exclude**/dto/**/exclude -Stephen 2009/10/29 anilkumar7...@gmail.com So in my case as the jar and compiled class files are being stored in directory F:/ARL/HIS/src/target/ and F:/ARL/HIS/src/classes/ , the relative to the class files will be F:/ARL/HIS/src/target/../classes/ . In this case the jar file created should be empty but it includes all the class files coming under classes directory. Regards, Anil Stephen Connolly-2 wrote: specify includes/excludes relative to the path in the jar. 2009/10/29 anil.kumar anilkumar7...@gmail.com Requirement: In initial stage I will compile all the files coming under my project source directory. Finally at the time of making the jar I need to selectively include and exclude certain files. The files which are to be included and excluded comes under my project source directory. My Project source directory : F:/ARL/HIS/src/ I am able to successfully compile all the files coming under my source directory. It is being saved in the location : F:/ARL/HIS/src/classes/ Sample code to include and exclude class files to make the jar file. plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId executions execution phasepackage/phase goals goaljar/goal /goals configuration classifierclient/classifier excludes exclude F:\ARL\HIS\src\classes\*.class/exclude// added for testing purpose to check if exclude tags work or not /excludes /configuration /execution /executions /plugin While executing the goal mvn org.apache.maven.plugins:maven-jar-plugin:jar , for making the jar file it takes all the files coming under classes directory where as i have specifically mentioned it not to be included while making the jar file. Where am I going wrong ? -- View this message in context: http://www.nabble.com/Selectively-include-and-exclude-class-file-while-building-the-artifact-tp26107145p26107145.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 Quoted from: http://www.nabble.com/Selectively-include-and-exclude-class-file-while-building-the-artifact-tp26107145p26107471.html -- View this message in context: http://www.nabble.com/Selectively-include-and-exclude-class-file-while-building-the-artifact-tp26107145p26109882.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 -- View this message in context: http://www.nabble.com/Selectively-include-and-exclude-class-file-while-building-the-artifact-tp26107145p26110534.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe,
Re: Selectively include and exclude class file while building the artifact
are you using backslashes? jar files do not have backslashes 2009/10/29 anil.kumar anilkumar7...@gmail.com Wanted to know one thing .Is the issue related to the way I have named the path to be mentioned in exclude tag. I have tried out all possible combination's . Still not working. Stephen Connolly-2 wrote: well just clobber it with a **/ as the prefix ;-) 2009/10/29 anil.kumar anilkumar7...@gmail.com Tried this as well. Not working. Stephen Connolly-2 wrote: you might require a leading / 2009/10/29 anil.kumar anilkumar7...@gmail.com Stephen, I thought by emailing is the only way you will be notified when I reply to the topic unless you sub scribe to the thread. Hence forth I will only post my queries in the forum. Thanks for letting me know. Coming to the topic ,it didn't work out. I will give this a try once more else I may have to look for other possible alternatives like maven-assembly-plugin. Thanks for your time. Stephen Connolly-2 wrote: Anil, Please reply to the list so that others may find the solutions to the problem (i.e. let google be their friend) To answer your question: Nope... I said the path *_in the jar_* so to exclude the class com.foo.bar.Manchu you would use excludecom/foo/bar/Manchu.class/exclude to exclude the entire com.foo.bar package you would use excludecom/foo/bar/**/exclude and to exclude all the dto packages you would use something like exclude**/dto/**/exclude -Stephen 2009/10/29 anilkumar7...@gmail.com So in my case as the jar and compiled class files are being stored in directory F:/ARL/HIS/src/target/ and F:/ARL/HIS/src/classes/ , the relative to the class files will be F:/ARL/HIS/src/target/../classes/ . In this case the jar file created should be empty but it includes all the class files coming under classes directory. Regards, Anil Stephen Connolly-2 wrote: specify includes/excludes relative to the path in the jar. 2009/10/29 anil.kumar anilkumar7...@gmail.com Requirement: In initial stage I will compile all the files coming under my project source directory. Finally at the time of making the jar I need to selectively include and exclude certain files. The files which are to be included and excluded comes under my project source directory. My Project source directory : F:/ARL/HIS/src/ I am able to successfully compile all the files coming under my source directory. It is being saved in the location : F:/ARL/HIS/src/classes/ Sample code to include and exclude class files to make the jar file. plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId executions execution phasepackage/phase goals goaljar/goal /goals configuration classifierclient/classifier excludes exclude F:\ARL\HIS\src\classes\*.class/exclude// added for testing purpose to check if exclude tags work or not /excludes /configuration /execution /executions /plugin While executing the goal mvn org.apache.maven.plugins:maven-jar-plugin:jar , for making the jar file it takes all the files coming under classes directory where as i have specifically mentioned it not to be included while making the jar file. Where am I going wrong ? -- View this message in context: http://www.nabble.com/Selectively-include-and-exclude-class-file-while-building-the-artifact-tp26107145p26107145.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 Quoted from: http://www.nabble.com/Selectively-include-and-exclude-class-file-while-building-the-artifact-tp26107145p26107471.html -- View this message in context: http://www.nabble.com/Selectively-include-and-exclude-class-file-while-building-the-artifact-tp26107145p26109882.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 -- View this
Re: Selectively include and exclude class file while building the artifact
There are files making use of package com.ADHOC which i need to ignore while making the jar file. So I tried to exclude them in the jar by using the following excludecom/ADHOC /**/exclude exclude**/com/ADHOC /**/exclude In both the ways it didn't work out. Stephen Connolly-2 wrote: are you using backslashes? jar files do not have backslashes 2009/10/29 anil.kumar anilkumar7...@gmail.com Wanted to know one thing .Is the issue related to the way I have named the path to be mentioned in exclude tag. I have tried out all possible combination's . Still not working. Stephen Connolly-2 wrote: well just clobber it with a **/ as the prefix ;-) 2009/10/29 anil.kumar anilkumar7...@gmail.com Tried this as well. Not working. Stephen Connolly-2 wrote: you might require a leading / 2009/10/29 anil.kumar anilkumar7...@gmail.com Stephen, I thought by emailing is the only way you will be notified when I reply to the topic unless you sub scribe to the thread. Hence forth I will only post my queries in the forum. Thanks for letting me know. Coming to the topic ,it didn't work out. I will give this a try once more else I may have to look for other possible alternatives like maven-assembly-plugin. Thanks for your time. Stephen Connolly-2 wrote: Anil, Please reply to the list so that others may find the solutions to the problem (i.e. let google be their friend) To answer your question: Nope... I said the path *_in the jar_* so to exclude the class com.foo.bar.Manchu you would use excludecom/foo/bar/Manchu.class/exclude to exclude the entire com.foo.bar package you would use excludecom/foo/bar/**/exclude and to exclude all the dto packages you would use something like exclude**/dto/**/exclude -Stephen 2009/10/29 anilkumar7...@gmail.com So in my case as the jar and compiled class files are being stored in directory F:/ARL/HIS/src/target/ and F:/ARL/HIS/src/classes/ , the relative to the class files will be F:/ARL/HIS/src/target/../classes/ . In this case the jar file created should be empty but it includes all the class files coming under classes directory. Regards, Anil Stephen Connolly-2 wrote: specify includes/excludes relative to the path in the jar. 2009/10/29 anil.kumar anilkumar7...@gmail.com Requirement: In initial stage I will compile all the files coming under my project source directory. Finally at the time of making the jar I need to selectively include and exclude certain files. The files which are to be included and excluded comes under my project source directory. My Project source directory : F:/ARL/HIS/src/ I am able to successfully compile all the files coming under my source directory. It is being saved in the location : F:/ARL/HIS/src/classes/ Sample code to include and exclude class files to make the jar file. plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId executions execution phasepackage/phase goals goaljar/goal /goals configuration classifierclient/classifier excludes exclude F:\ARL\HIS\src\classes\*.class/exclude// added for testing purpose to check if exclude tags work or not /excludes /configuration /execution /executions /plugin While executing the goal mvn org.apache.maven.plugins:maven-jar-plugin:jar , for making the jar file it takes all the files coming under classes directory where as i have specifically mentioned it not to be included while making the jar file. Where am I going wrong ? -- View this message in context: http://www.nabble.com/Selectively-include-and-exclude-class-file-while-building-the-artifact-tp26107145p26107145.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 Quoted from: http://www.nabble.com/Selectively-include-and-exclude-class-file-while-building-the-artifact-tp26107145p26107471.html -- View this message in context:
Re: resouce files not in the built jar
ah! no, don't do that. Resources belong in /src/main/resources and are automatically pulled into the jar. Manually adding the java folder just undoes some of the maven conventions. On Wed, Oct 28, 2009 at 10:22 AM, KOUKI Fakhreddine kouki.fakhredd...@gmail.com wrote: Hi , Put this on your Pom : build ... resources resource directorysrc/main/java/directory excludes exclude**/*.java/exclude /excludes /resource /resources /build On 10/28/09, thomas2004 thomas200...@yahoo.de wrote: Hi all, I use maven 2.0.9 and Eclipse to build my program. But I met a strange thing: I put some resource files such as context.xml in the same package as my java files. But after I built the project/program with mvn clean package, I can't find the context.xml inside the jar. That's the reason why I got FileNotFoundException as I run the program. Someone knows why? -- View this message in context: http://www.nabble.com/resouce-files-not-in-the-built-jar-tp26095189p26095189.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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Aspectj jars refuse to get imported
Renaming it and installing it into your repo won't change anything if it's getting added to the classpath on the commandline, so NO don't do that. I believe someone already posted how to configure eclipse:eclipse to add the aspect support. Or you can install m2eclipse and use that instead. On Sun, Oct 25, 2009 at 8:42 AM, Yaakov Chaikin yaakov.chai...@gmail.com wrote: I spoke too soon. It does work on the command line... Given that it now work on the command line, are you still suggesting that I NOT renaming it and deploy it in our archiva under a different name? I guess, I am not sure how I would force it into Eclipse's .classpath any other way. Thanks, Yaakov. On Fri, Oct 23, 2009 at 7:39 PM, Brian Fox bri...@infinity.nu wrote: Can you send us some build logs with -X enabled? There is nothing in core that should be excluding aspectj, so something else is at play here. And loading them with a different coordinate into your repo manager is going to cause problems later, that is just patching the symptoms On Fri, Oct 23, 2009 at 4:09 PM, Yaakov Chaikin yaakov.chai...@gmail.com wrote: Oh, I see... However, classpath I was referring to was just regular classpath, not .classpath of eclipse... It's excluded from the regular Java classpath as well for some reason. Yaakov. On Fri, Oct 23, 2009 at 3:57 PM, Nick Stolwijk nick.stolw...@gmail.com wrote: The plugins have their own versioning. He means the 2.8 release of the eclipse plugin. Hth, Nick Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012 WS Haarlem http://www.iprofs.nl On Fri, Oct 23, 2009 at 7:42 PM, Yaakov Chaikin yaakov.chai...@gmail.comwrote: This won't happen anymore in (unreleased) 2.8. I agree with Barrie that this should be documented for users of 2.6 and 2.7. Anyone want to submit a patch for one of the help pages? Version 2.8 of maven? I am running maven 2.0.9 which IS released... From what I see on the maven's page, the latest version is 2.2.1. They are working on 2.8 already?? Yaakov. - 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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [Fwd: Threads in a plug-in]
Maven just exits when it's done and then the jdk pulls everything down. Isn't there a flag you can set on a thread to mark it as a daemon thread, and then the system waits before killing it? On Wed, Oct 28, 2009 at 9:20 AM, Gajo Csaba csaba.g...@cosylab.com wrote: Good idea! I was actually hoping there was some switch I can set in Maven to tell it not to terminate my thread, but I guess your idea would work fine as well. Thanks! Csaba Stephen Connolly wrote: add a second goal the first goal will store some thread completion object in MavenSession or in a Class level static field When all threads are finished the completion object will be updated by the last thread The second goal blocks until the completion object is completed. Then add the second goal execution to your project at the appropriate phase where you need the execution to have completed... for example if you start the threads in the process-sources phase, you might be happy to let them run in the background until the test phase has completed, but they must be finished by the time the package phase runs, so I would bind your execution of the second goal to the test phase -Stephen 2009/10/28 Gajo Csaba csaba.g...@cosylab.com - 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: [Fwd: Threads in a plug-in]
Hello, Actually it is the other way around. Daemon threads will not hold up JVM from exiting, but non-deamon threads will. Marks this thread as either a daemon thread or a user thread. The Java Virtual Machine exits when the only threads running are all daemon threads. The daemon flag will be set if the creating thread is a daemon thread. Maybe force the setDaemon to false on the newly created thread and that may give you desired effect. -jr Brian Fox wrote: Maven just exits when it's done and then the jdk pulls everything down. Isn't there a flag you can set on a thread to mark it as a daemon thread, and then the system waits before killing it? On Wed, Oct 28, 2009 at 9:20 AM, Gajo Csaba csaba.g...@cosylab.com wrote: Good idea! I was actually hoping there was some switch I can set in Maven to tell it not to terminate my thread, but I guess your idea would work fine as well. Thanks! Csaba Stephen Connolly wrote: add a second goal the first goal will store some thread completion object in MavenSession or in a Class level static field When all threads are finished the completion object will be updated by the last thread The second goal blocks until the completion object is completed. Then add the second goal execution to your project at the appropriate phase where you need the execution to have completed... for example if you start the threads in the process-sources phase, you might be happy to let them run in the background until the test phase has completed, but they must be finished by the time the package phase runs, so I would bind your execution of the second goal to the test phase -Stephen 2009/10/28 Gajo Csaba csaba.g...@cosylab.com - 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: [Fwd: Threads in a plug-in]
I think Maven executes a System.exit at the end, which will terminate all threads, regardless of daemon state. With regards, Nick Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012 WS Haarlem http://www.iprofs.nl On Thu, Oct 29, 2009 at 1:09 PM, James Russo j...@halo3.net wrote: Hello, Actually it is the other way around. Daemon threads will not hold up JVM from exiting, but non-deamon threads will. Marks this thread as either a daemon thread or a user thread. The Java Virtual Machine exits when the only threads running are all daemon threads. The daemon flag will be set if the creating thread is a daemon thread. Maybe force the setDaemon to false on the newly created thread and that may give you desired effect. -jr Brian Fox wrote: Maven just exits when it's done and then the jdk pulls everything down. Isn't there a flag you can set on a thread to mark it as a daemon thread, and then the system waits before killing it? On Wed, Oct 28, 2009 at 9:20 AM, Gajo Csaba csaba.g...@cosylab.com wrote: Good idea! I was actually hoping there was some switch I can set in Maven to tell it not to terminate my thread, but I guess your idea would work fine as well. Thanks! Csaba Stephen Connolly wrote: add a second goal the first goal will store some thread completion object in MavenSession or in a Class level static field When all threads are finished the completion object will be updated by the last thread The second goal blocks until the completion object is completed. Then add the second goal execution to your project at the appropriate phase where you need the execution to have completed... for example if you start the threads in the process-sources phase, you might be happy to let them run in the background until the test phase has completed, but they must be finished by the time the package phase runs, so I would bind your execution of the second goal to the test phase -Stephen 2009/10/28 Gajo Csaba csaba.g...@cosylab.com - 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: [Fwd: Threads in a plug-in]
Which is the main class of maven? I found in org.apache.maven.cli.MavenCli this as the last line of the public static void main method, so maybe this is it: System.exit( result ); Regards, Csaba Nick Stolwijk wrote: I think Maven executes a System.exit at the end, which will terminate all threads, regardless of daemon state. With regards, Nick Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012 WS Haarlem http://www.iprofs.nl On Thu, Oct 29, 2009 at 1:09 PM, James Russo j...@halo3.net wrote: Hello, Actually it is the other way around. Daemon threads will not hold up JVM from exiting, but non-deamon threads will. Marks this thread as either a daemon thread or a user thread. The Java Virtual Machine exits when the only threads running are all daemon threads. The daemon flag will be set if the creating thread is a daemon thread. Maybe force the setDaemon to false on the newly created thread and that may give you desired effect. -jr Brian Fox wrote: Maven just exits when it's done and then the jdk pulls everything down. Isn't there a flag you can set on a thread to mark it as a daemon thread, and then the system waits before killing it? On Wed, Oct 28, 2009 at 9:20 AM, Gajo Csaba csaba.g...@cosylab.com wrote: Good idea! I was actually hoping there was some switch I can set in Maven to tell it not to terminate my thread, but I guess your idea would work fine as well. Thanks! Csaba Stephen Connolly wrote: add a second goal the first goal will store some thread completion object in MavenSession or in a Class level static field When all threads are finished the completion object will be updated by the last thread The second goal blocks until the completion object is completed. Then add the second goal execution to your project at the appropriate phase where you need the execution to have completed... for example if you start the threads in the process-sources phase, you might be happy to let them run in the background until the test phase has completed, but they must be finished by the time the package phase runs, so I would bind your execution of the second goal to the test phase -Stephen 2009/10/28 Gajo Csaba csaba.g...@cosylab.com - 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: Aspectj jars refuse to get imported
Yup, it was already posted in the beginning of this thread. Yaakov, do not rename your jars but simply configure the plugin like you were told to before: configuration ajdtVersionnone/ajdtVersion /configuration http://jira.codehaus.org/browse/MECLIPSE-594 Paul On Thu, Oct 29, 2009 at 6:56 AM, Brian Fox bri...@infinity.nu wrote: Renaming it and installing it into your repo won't change anything if it's getting added to the classpath on the commandline, so NO don't do that. I believe someone already posted how to configure eclipse:eclipse to add the aspect support. Or you can install m2eclipse and use that instead. On Sun, Oct 25, 2009 at 8:42 AM, Yaakov Chaikin yaakov.chai...@gmail.com wrote: I spoke too soon. It does work on the command line... Given that it now work on the command line, are you still suggesting that I NOT renaming it and deploy it in our archiva under a different name? I guess, I am not sure how I would force it into Eclipse's .classpath any other way. Thanks, Yaakov. On Fri, Oct 23, 2009 at 7:39 PM, Brian Fox bri...@infinity.nu wrote: Can you send us some build logs with -X enabled? There is nothing in core that should be excluding aspectj, so something else is at play here. And loading them with a different coordinate into your repo manager is going to cause problems later, that is just patching the symptoms On Fri, Oct 23, 2009 at 4:09 PM, Yaakov Chaikin yaakov.chai...@gmail.com wrote: Oh, I see... However, classpath I was referring to was just regular classpath, not .classpath of eclipse... It's excluded from the regular Java classpath as well for some reason. Yaakov. On Fri, Oct 23, 2009 at 3:57 PM, Nick Stolwijk nick.stolw...@gmail.com wrote: The plugins have their own versioning. He means the 2.8 release of the eclipse plugin. Hth, Nick Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012 WS Haarlem http://www.iprofs.nl On Fri, Oct 23, 2009 at 7:42 PM, Yaakov Chaikin yaakov.chai...@gmail.comwrote: This won't happen anymore in (unreleased) 2.8. I agree with Barrie that this should be documented for users of 2.6 and 2.7. Anyone want to submit a patch for one of the help pages? Version 2.8 of maven? I am running maven 2.0.9 which IS released... From what I see on the maven's page, the latest version is 2.2.1. They are working on 2.8 already?? Yaakov. - 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 - 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: Selectively include and exclude class file while building the artifact
giv e us a more full pom snippet 2009/10/29 anil.kumar anilkumar7...@gmail.com There are files making use of package com.ADHOC which i need to ignore while making the jar file. So I tried to exclude them in the jar by using the following excludecom/ADHOC /**/exclude exclude**/com/ADHOC /**/exclude In both the ways it didn't work out. Stephen Connolly-2 wrote: are you using backslashes? jar files do not have backslashes 2009/10/29 anil.kumar anilkumar7...@gmail.com Wanted to know one thing .Is the issue related to the way I have named the path to be mentioned in exclude tag. I have tried out all possible combination's . Still not working. Stephen Connolly-2 wrote: well just clobber it with a **/ as the prefix ;-) 2009/10/29 anil.kumar anilkumar7...@gmail.com Tried this as well. Not working. Stephen Connolly-2 wrote: you might require a leading / 2009/10/29 anil.kumar anilkumar7...@gmail.com Stephen, I thought by emailing is the only way you will be notified when I reply to the topic unless you sub scribe to the thread. Hence forth I will only post my queries in the forum. Thanks for letting me know. Coming to the topic ,it didn't work out. I will give this a try once more else I may have to look for other possible alternatives like maven-assembly-plugin. Thanks for your time. Stephen Connolly-2 wrote: Anil, Please reply to the list so that others may find the solutions to the problem (i.e. let google be their friend) To answer your question: Nope... I said the path *_in the jar_* so to exclude the class com.foo.bar.Manchu you would use excludecom/foo/bar/Manchu.class/exclude to exclude the entire com.foo.bar package you would use excludecom/foo/bar/**/exclude and to exclude all the dto packages you would use something like exclude**/dto/**/exclude -Stephen 2009/10/29 anilkumar7...@gmail.com So in my case as the jar and compiled class files are being stored in directory F:/ARL/HIS/src/target/ and F:/ARL/HIS/src/classes/ , the relative to the class files will be F:/ARL/HIS/src/target/../classes/ . In this case the jar file created should be empty but it includes all the class files coming under classes directory. Regards, Anil Stephen Connolly-2 wrote: specify includes/excludes relative to the path in the jar. 2009/10/29 anil.kumar anilkumar7...@gmail.com Requirement: In initial stage I will compile all the files coming under my project source directory. Finally at the time of making the jar I need to selectively include and exclude certain files. The files which are to be included and excluded comes under my project source directory. My Project source directory : F:/ARL/HIS/src/ I am able to successfully compile all the files coming under my source directory. It is being saved in the location : F:/ARL/HIS/src/classes/ Sample code to include and exclude class files to make the jar file. plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId executions execution phasepackage/phase goals goaljar/goal /goals configuration classifierclient/classifier excludes exclude F:\ARL\HIS\src\classes\*.class/exclude// added for testing purpose to check if exclude tags work or not /excludes /configuration /execution /executions /plugin While executing the goal mvn org.apache.maven.plugins:maven-jar-plugin:jar , for making the jar file it takes all the files coming under classes directory where as i have specifically mentioned it not to be included while making the jar file. Where am I going wrong ? -- View this message in context: http://www.nabble.com/Selectively-include-and-exclude-class-file-while-building-the-artifact-tp26107145p26107145.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 Quoted from:
[ANN] Apache Source-Release Assembly Descriptor 1.0.1 Released
The Maven team is pleased to announce the release of Apache Source-Release Assembly Descriptor, version 1.0.1. This is a standardized assembly descriptor for use in the maven-assembly-plugin. Source-release artifacts are archives which contain the full project structure (sources only, no build output) that are the subject of an ASF release vote. The new version of the descriptor fixes the erroneous inclusion of some build output in the source archive. Please see http://jira.codehaus.org/browse/MASSEMBLY-446 for more details on the issue. http://maven.apache.org/apache-resource-bundles/apache-source-release-assembly-descriptor/ This assembly descriptor should be coming to a parent POM near you, and should eventually be an automatic part of every ASF release. For now, it has been configured into the release process for Maven projects that inherit from maven-parent version 14 (also recently released). If you want to try out the source-release descriptor in the meantime, you can include a configuration like the following: build plugins plugin artifactIdmaven-assembly-plugin/artifactId version2.2-beta-4/version dependencies dependency groupIdorg.apache.apache.resources/groupId artifactIdapache-source-release-assembly-descriptor/artifactId version1.0.1/version /dependency dependency !-- NOTE: The fix for PLXUTILS-120 is crucial for the new assembly descriptor -- groupIdorg.codehaus.plexus/groupId artifactIdplexus-utils/artifactId version2.0.1/version /dependency /dependencies executions execution idsource-release/id phasepackage/phase goals goalsingle/goal /goals configuration descriptorRefs descriptorRefsource-release/descriptorRef /descriptorRefs tarLongFileModegnu/tarLongFileMode runOnlyAtExecutionRoottrue/runOnlyAtExecutionRoot /configuration /execution /executions /plugin /plugins /build Enjoy, The Maven Team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Selectively include and exclude class file while building the artifact
As requested I have added more details about the pom.xml . I hope this would be sufficient . ?xml version=1.0 encoding=UTF-8? 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/maven-v4_0_0.xsd; basedir=. modelVersion4.0.0/modelVersion groupIdHIS/groupId artifactIdHIS/artifactId version1.0/version packagingjar/packaging nameHIS Project/name dependencies // Only part of the dependencies are mentioned dependency groupIdxerces/groupId artifactIdxerces/artifactId version2.4.0/version /dependency dependency groupIdxml-apis/groupId artifactIdxml-apis/artifactId version2.0.0/version /dependency dependency groupIdcommons-digester/groupId artifactIdcommons-digester/artifactId version1.3/version /dependency dependencies build plugins plugin groupIdorg.codehaus.mojo/groupId artifactIdbuild-helper-maven-plugin/artifactId version1.3/version executions execution idfirst/id goals goaladd-source/goal /goals phasegenerate-sources/phase configuration sources sourceF:/ARL/HIS/src//source //Compile all the files under source directory /sources /configuration /execution /executions /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId executions execution phasepackage/phase goals goaljar/goal // Execute the goal using mvn org.apache.maven.plugins:maven-jar-plugin:jar /goals configuration classifierclient/classifier excludes exclude**/com/ADHOC/*/exclude /excludes /configuration /execution /executions /plugin /plugins outputDirectoryclasses/outputDirectory /build /project Stephen Connolly-2 wrote: giv e us a more full pom snippet 2009/10/29 anil.kumar anilkumar7...@gmail.com There are files making use of package com.ADHOC which i need to ignore while making the jar file. So I tried to exclude them in the jar by using the following excludecom/ADHOC /**/exclude exclude**/com/ADHOC /**/exclude In both the ways it didn't work out. Stephen Connolly-2 wrote: are you using backslashes? jar files do not have backslashes 2009/10/29 anil.kumar anilkumar7...@gmail.com Wanted to know one thing .Is the issue related to the way I have named the path to be mentioned in exclude tag. I have tried out all possible combination's . Still not working. Stephen Connolly-2 wrote: well just clobber it with a **/ as the prefix ;-) 2009/10/29 anil.kumar anilkumar7...@gmail.com Tried this as well. Not working. Stephen Connolly-2 wrote: you might require a leading / 2009/10/29 anil.kumar anilkumar7...@gmail.com Stephen, I thought by emailing is the only way you will be notified when I reply to the topic unless you sub scribe to the thread. Hence forth I will only post my queries in the forum. Thanks for letting me know. Coming to the topic ,it didn't work out. I will give this a try once more else I may have to look for other possible alternatives like maven-assembly-plugin. Thanks for your time. Stephen Connolly-2 wrote: Anil, Please reply to the list so that others may find the solutions to the problem (i.e. let google be their friend) To answer your question: Nope... I said the path *_in the jar_* so to exclude the class com.foo.bar.Manchu you would use excludecom/foo/bar/Manchu.class/exclude to exclude the entire com.foo.bar package you would use excludecom/foo/bar/**/exclude and to exclude all the dto packages you would use something like exclude**/dto/**/exclude -Stephen 2009/10/29 anilkumar7...@gmail.com So in my
How can I create a dependency on my dar archive?
Hi all Justin explained how to create a new packaging type: http://stackoverflow.com/questions/1427722/how-do-i-create-a-new-packagi ng-type-for-maven So I now have my .dar type. Cool :-) BUT, I also need to create a dependency to that type. As matters stand, it seems that a dependency must be a .jar file. The dependency lookup fails if it is a .dar file. Any ideas? Thanks Nathan -- Nathan Sowatskey (nsowa...@cisco.com) - Technical Leader, NMTG XMP - +34-638-083-675 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Aspectj jars refuse to get imported
Right... Forgot about that one. Thanks. On Thu, Oct 29, 2009 at 8:36 AM, Paul Benedict pbened...@apache.org wrote: Yup, it was already posted in the beginning of this thread. Yaakov, do not rename your jars but simply configure the plugin like you were told to before: configuration ajdtVersionnone/ajdtVersion /configuration http://jira.codehaus.org/browse/MECLIPSE-594 Paul On Thu, Oct 29, 2009 at 6:56 AM, Brian Fox bri...@infinity.nu wrote: Renaming it and installing it into your repo won't change anything if it's getting added to the classpath on the commandline, so NO don't do that. I believe someone already posted how to configure eclipse:eclipse to add the aspect support. Or you can install m2eclipse and use that instead. On Sun, Oct 25, 2009 at 8:42 AM, Yaakov Chaikin yaakov.chai...@gmail.com wrote: I spoke too soon. It does work on the command line... Given that it now work on the command line, are you still suggesting that I NOT renaming it and deploy it in our archiva under a different name? I guess, I am not sure how I would force it into Eclipse's .classpath any other way. Thanks, Yaakov. On Fri, Oct 23, 2009 at 7:39 PM, Brian Fox bri...@infinity.nu wrote: Can you send us some build logs with -X enabled? There is nothing in core that should be excluding aspectj, so something else is at play here. And loading them with a different coordinate into your repo manager is going to cause problems later, that is just patching the symptoms On Fri, Oct 23, 2009 at 4:09 PM, Yaakov Chaikin yaakov.chai...@gmail.com wrote: Oh, I see... However, classpath I was referring to was just regular classpath, not .classpath of eclipse... It's excluded from the regular Java classpath as well for some reason. Yaakov. On Fri, Oct 23, 2009 at 3:57 PM, Nick Stolwijk nick.stolw...@gmail.com wrote: The plugins have their own versioning. He means the 2.8 release of the eclipse plugin. Hth, Nick Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012 WS Haarlem http://www.iprofs.nl On Fri, Oct 23, 2009 at 7:42 PM, Yaakov Chaikin yaakov.chai...@gmail.comwrote: This won't happen anymore in (unreleased) 2.8. I agree with Barrie that this should be documented for users of 2.6 and 2.7. Anyone want to submit a patch for one of the help pages? Version 2.8 of maven? I am running maven 2.0.9 which IS released... From what I see on the maven's page, the latest version is 2.2.1. They are working on 2.8 already?? Yaakov. - 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 - 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: How can I create a dependency on my dar archive?
See the pom reference [1]. You will need to set the type to dar instead of jar. [1] http://maven.apache.org/pom.html#Dependencies Hth, Nick Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012 WS Haarlem http://www.iprofs.nl On Thu, Oct 29, 2009 at 2:09 PM, nsowatsk nsowa...@cisco.com wrote: Hi all Justin explained how to create a new packaging type: http://stackoverflow.com/questions/1427722/how-do-i-create-a-new-packagi ng-type-for-mavenhttp://stackoverflow.com/questions/1427722/how-do-i-create-a-new-packagi%0Ang-type-for-maven So I now have my .dar type. Cool :-) BUT, I also need to create a dependency to that type. As matters stand, it seems that a dependency must be a .jar file. The dependency lookup fails if it is a .dar file. Any ideas? Thanks Nathan -- Nathan Sowatskey (nsowa...@cisco.com) - Technical Leader, NMTG XMP - +34-638-083-675 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Encrypting type in maven
That is the way Maven 2.1.0+ supports encrypted server passwords stored in your settings.xml. What is the exact problem you're seeing. Please post some logs. /Anders On Thu, Oct 29, 2009 at 12:18, Antonio Gonzalez antonio.gonzalez.fajardo@juntadeandalucia.es wrote: Hi, I will use archiva as repository with maven, I have configured archiva for connect to LDAP, to realize mvn deploy, I use encrypted password as it is specified in the documentation ( http://maven.apache.org/guides/mini/guide-encryption.html#How_to_keep_the_m aster_password_on_removable_drive), but I have a doubt and it is that not that type of encrypting uses maven for the passwords, might someone say to me that type of Encryption is in use for encrypting the password? Thanks!
Re: How can I create a dependency on my dar archive?
Cool, thanks, that worked! Now I can go get lunch ;-) Nathan On 29/10/2009 14:13, Nick Stolwijk nick.stolw...@gmail.com wrote: See the pom reference [1]. You will need to set the type to dar instead of jar. [1] http://maven.apache.org/pom.html#Dependencies Hth, Nick Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012 WS Haarlem http://www.iprofs.nl On Thu, Oct 29, 2009 at 2:09 PM, nsowatsk nsowa...@cisco.com wrote: Hi all Justin explained how to create a new packaging type: http://stackoverflow.com/questions/1427722/how-do-i-create-a-new-packagi ng-type-for-mavenhttp://stackoverflow.com/questions/1427722/how-do-i-create- a-new-packagi%0Ang-type-for-maven So I now have my .dar type. Cool :-) BUT, I also need to create a dependency to that type. As matters stand, it seems that a dependency must be a .jar file. The dependency lookup fails if it is a .dar file. Any ideas? Thanks Nathan -- Nathan Sowatskey (nsowa...@cisco.com) - Technical Leader, NMTG XMP - +34-638-083-675 - 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
problem in pom aggregation
Hi All, I am having one requirement which i am unable to meet through pom aggregation. I am having 8 modules.i want to execute 'test' goal in one module.and in other 7 modules i should do clean,install and deploy. I will run from hudson.how can I manage to fire only 'test' goal in one module and install/deploy in other 7 modules. Thanks, Debasis -- View this message in context: http://www.nabble.com/problem-in-pom-aggregation-tp26112951p26112951.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: Easiest way to build in connectionless environment?
You mean like mvn dependency:copy-dependencies? Also take a look at dependency:go-offline On Fri, Oct 16, 2009 at 5:42 AM, janneefef jannepostilis...@gmail.com wrote: janneefef wrote: We're using maven day to day in normal developer environment. People do their builds on the local computer and dependencies get automatically fetched to the local repositories. Now occasionally there's need to build project X on some computer Y which has no internet connection. How can this be done most easily? Preferrably so that there's no need to install any additional software such as repository managers on target computer Y. Ideally there would be a simple zip packet with instructions 1-2-3... to build the software. One idea is to zip someone's local repository and explode it on target computer Y before maven buidling there. But this gets a bit messy if local repository contains a lot of dependencies that are not used in project X. Is there any integrated support build into maven itself for this kind of use case? Or maybe some plugins that would help? One thing which would be helpful, would be if there was a command / plugin which would dump all the dependencies to a hierachy, that could be copied to target computer's local repository. -- View this message in context: http://www.nabble.com/Easiest-way-to-build-in-connectionless-environment--tp25922486p25922574.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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: problem in pom aggregation
freestyle use profiles to define the modules -Peverything-except-test deploy | -Ptest-only test 2009/10/29 Mr Debasis debasis1...@gmail.com Hi All, I am having one requirement which i am unable to meet through pom aggregation. I am having 8 modules.i want to execute 'test' goal in one module.and in other 7 modules i should do clean,install and deploy. I will run from hudson.how can I manage to fire only 'test' goal in one module and install/deploy in other 7 modules. Thanks, Debasis -- View this message in context: http://www.nabble.com/problem-in-pom-aggregation-tp26112951p26112951.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
use case with classifiers
Hi all. I'm trying to fix MECLIPSE-615 [1]. The fix that seems fastest to me might cause an issue if you include multiple dependencies from the same module, using the same scope. I don't know if this use case makes any sense since I've only used classifiers for test-jar's. Does anyone use something (roughly) along the lines of: dependency groupIdcom.example/groupId artifactIdmyArtifact/artifactId version1.2.3/version classifier*bin*/classifier scopecompile/scope /dependency dependency groupIdcom.example/groupId artifactIdmyArtifact/artifactId version1.2.3/version classifier*dev*/classifier scopecompile/scope /dependency dependency groupIdcom.example/groupId artifactIdmyArtifact/artifactId version1.2.3/version classifier*prod*/classifier scopecompile/scope /dependency Same groupId, artifactId, version, and scope, just with different classifiers? Is this a valid use case of maven? Thanks for your time! Jim [1] http://jira.codehaus.org/browse/MECLIPSE-615
Re: Wagon protocol 'scm' doesn't support directory copying
Finally I've been able to try this and it worked like a charm copying my site files. I now face another problem. When I open an HTML file I don't get the HTML parsed, I get the file source. I know that this can be fixed by changing the svn properties to svn:mime-type=text/html. Can wagon-svn or Maven do this automatically for me? Best regards, The openmaximo.net Team http://www.openmaximo.net/ On Thu, Oct 8, 2009 at 11:48, Open Source Dept o...@openmaximo.net wrote: Thanks a lot, I'll try wagon-svn then. The openmaximo.net Team http://www.openmaximo.net/ On Mon, Oct 5, 2009 at 13:58, Edelson, Justin justin.edel...@mtvstaff.com wrote: Not with wagon-scm, but you can with https://wagon-svn.dev.java.net/. From: Open Source Dept [mailto:o...@openmaximo.net] Sent: Mon 10/5/2009 7:14 AM To: users@maven.apache.org Subject: Wagon protocol 'scm' doesn't support directory copying Hi everyone, I'm trying to deploy my maven site using wagon-scm but I'm getting this error: Wagon protocol 'scm' doesn't support directory copying. Is it possible to deploy a site using mvn site-deploy and an SVN repository? I'm using this 3 extensions: extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-scm/artifactId version1.0-alpha-4/version /extension extension groupIdorg.apache.maven.scm/groupId artifactIdmaven-scm-manager-plexus/artifactId version1.3-SNAPSHOT/version /extension extension groupIdorg.apache.maven.scm/groupId artifactIdmaven-scm-provider-svnexe/artifactId version1.3-SNAPSHOT/version /extension /extensions Best regards, -- The openmaximo.net Team http://www.openmaximo.net/
NAR assembly
I am now getting into building the assembly portion of this. I don't
think the nar is getting looked up correctly. The nar is placed in the
system as a x86-Windows-g++-jni.jar, but the assembly plugin is looking
for x86-Windows-jni.jar. Also, even though I am explicitly setting the
classifier, the output references x86-Windows-msvc. I am trying to
figure out how to get it so I can run the plugin in debug mode in
Eclipse so I can help unravel this.
Damon
[INFO] snapshot com.lifetouch.utility:ioutilities:1.1.0-SNAPSHOT:
checking for updates from snapshots
[INFO] [nar:nar-download {execution: default}]
[INFO] Using AOL: x86-Windows-msvc
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] nar not found
com.lifetouch.utility:ImagenomicPortraiturePluginDLL:nar:x86-Windows-jni
:0.0.1-SNAPSHOT
Embedded error: Unable to download the artifact from any repository
POM.XML
plugin
artifactIdmaven-assembly-plugin/artifactId
configuration
descriptors
descriptorsrc/main/assembly/assembly.xml/descriptor
/descriptors
/configuration
/plugin
plugin
artifactIdmaven-nar-plugin/artifactId
configuration
classifiers
classifierx86-Windows-g++/classifier
/classifiers
/configuration
executions
execution
goals
goalnar-download/goal
goalnar-unpack/goal
goalnar-assembly/goal
/goals
/execution
/executions
/plugin
ASSEBMLY.XML
assembly
iddistribution/id
formats
!-- can't seem to find reference to dir, which is what I
really want, guess I will unzip manually --
formatzip/format
/formats
includeBaseDirectoryfalse/includeBaseDirectory
dependencySets
dependencySet
unpackfalse/unpack
scoperuntime/scope
/dependencySet
/dependencySets
fileSets
fileSet
directorytarget/nar/lib/x86-Windows-g++/directory
outputDirectorylib/outputDirectory
includes
include*/include
/includes
/fileSet
fileSet
includes
include${project.basedir}/README*/include
include${project.basedir}/LICENSE*/include
include${project.basedir}/NOTICE*/include
/includes
/fileSet
fileSet
directory${project.build.directory}/directory
includes
include*.jar/include
/includes
/fileSet
/fileSets
/assembly
__
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
_
Re: use case with classifiers
Yes, it is a valid use case. My company does something kind of similar, but it's used for including two versions of the same artifact in the build (and in the ear/war) - for example, if we have a 2.1 and a 3.0 release of a project, and based on legacy reasons and transitive dependencies, we have to include both those jars in the build (which is safe because of package names not clashing). What we've done is used a classifier of 2.1 which allows maven to pick up both versions and not try and resolve the best one to include. We do have to push the artifacts out to the repository with both the unclassified and the classified artifacts, since not everyone needs to use the classifier. On Thu, Oct 29, 2009 at 9:01 AM, Jim Sellers jim.sell...@gmail.com wrote: Hi all. I'm trying to fix MECLIPSE-615 [1]. The fix that seems fastest to me might cause an issue if you include multiple dependencies from the same module, using the same scope. I don't know if this use case makes any sense since I've only used classifiers for test-jar's. Does anyone use something (roughly) along the lines of: dependency groupIdcom.example/groupId artifactIdmyArtifact/artifactId version1.2.3/version classifier*bin*/classifier scopecompile/scope /dependency dependency groupIdcom.example/groupId artifactIdmyArtifact/artifactId version1.2.3/version classifier*dev*/classifier scopecompile/scope /dependency dependency groupIdcom.example/groupId artifactIdmyArtifact/artifactId version1.2.3/version classifier*prod*/classifier scopecompile/scope /dependency Same groupId, artifactId, version, and scope, just with different classifiers? Is this a valid use case of maven? Thanks for your time! Jim [1] http://jira.codehaus.org/browse/MECLIPSE-615
RE: NAR assembly
assuming you're NOT implementing on doze
can you use a profile to steer the execution away from msvc and towards
x86-Windows-g++
?
Martin Gainty
__
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung.
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est
interdite. Ce message sert à l'information seulement et n'aura pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
Subject: NAR assembly
Date: Thu, 29 Oct 2009 11:30:47 -0500
From: dajacob...@lifetouch.com
To: users@maven.apache.org
I am now getting into building the assembly portion of this. I don't
think the nar is getting looked up correctly. The nar is placed in the
system as a x86-Windows-g++-jni.jar, but the assembly plugin is looking
for x86-Windows-jni.jar. Also, even though I am explicitly setting the
classifier, the output references x86-Windows-msvc. I am trying to
figure out how to get it so I can run the plugin in debug mode in
Eclipse so I can help unravel this.
Damon
[INFO] snapshot com.lifetouch.utility:ioutilities:1.1.0-SNAPSHOT:
checking for updates from snapshots
[INFO] [nar:nar-download {execution: default}]
[INFO] Using AOL: x86-Windows-msvc
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] nar not found
com.lifetouch.utility:ImagenomicPortraiturePluginDLL:nar:x86-Windows-jni
:0.0.1-SNAPSHOT
Embedded error: Unable to download the artifact from any repository
POM.XML
plugin
artifactIdmaven-assembly-plugin/artifactId
configuration
descriptors
descriptorsrc/main/assembly/assembly.xml/descriptor
/descriptors
/configuration
/plugin
plugin
artifactIdmaven-nar-plugin/artifactId
configuration
classifiers
classifierx86-Windows-g++/classifier
/classifiers
/configuration
executions
execution
goals
goalnar-download/goal
goalnar-unpack/goal
goalnar-assembly/goal
/goals
/execution
/executions
/plugin
ASSEBMLY.XML
assembly
iddistribution/id
formats
!-- can't seem to find reference to dir, which is what I
really want, guess I will unzip manually --
formatzip/format
/formats
includeBaseDirectoryfalse/includeBaseDirectory
dependencySets
dependencySet
unpackfalse/unpack
scoperuntime/scope
/dependencySet
/dependencySets
fileSets
fileSet
directorytarget/nar/lib/x86-Windows-g++/directory
outputDirectorylib/outputDirectory
includes
include*/include
/includes
/fileSet
fileSet
includes
include${project.basedir}/README*/include
include${project.basedir}/LICENSE*/include
include${project.basedir}/NOTICE*/include
/includes
/fileSet
fileSet
directory${project.build.directory}/directory
includes
include*.jar/include
/includes
/fileSet
/fileSets
/assembly
__
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
_
_
New Windows 7: Find the right PC for you. Learn more.
Semi-automated application.xml generation
Hi, Is there a possibility to semi-automate application.xml generation? What I specifically want to do is this: Currently I use the maven ear plugin to create the application.xml. However, I need to register a module that should not be processed otherwise. This means, the only thing that should happen is that the application.xml contains a module description for that module. No files should be copied around and the module should not be contained in the ear (don't ask why). On the other hand, I don't want to create the complete application.xml manually. So I see two options: 1. let the maven ear plugin generate the application.xml but add the module definition in another way (maybe using filtering) 2. create a skeleton application.xml and add the other modules during the process-resources phase (filtering?) Is this possible? Or is there another way? Thanks in advance. Thomas
tracking down jetty/tomcat dependencies
I've got code that works fine when run as a pojo and fails when run in a webapp, either via tomcat:run or jetty:run. I suspect, because I can't think of anything else, that there is detritus in the 'system' classpaths of these containers. However, mvn dependency:tree does not tell me much about the maven-jetty-plugin. Neither does dependency:resolve-plugins. Is there some way to get a clearer view of this question?
RE: NAR assembly
Unfortunately my development is mandated to be done on Windows. I tried to use
classifier in the nar plugin configuration away from msvc with no luck.
Damon Jacobsen
-Original Message-
From: Martin Gainty [mailto:mgai...@hotmail.com]
Sent: Thursday, October 29, 2009 9:50 AM
To: users@maven.apache.org
Subject: RE: NAR assembly
assuming you're NOT implementing on doze
can you use a profile to steer the execution away from msvc and towards
x86-Windows-g++
?
Martin Gainty
__
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung.
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est
interdite. Ce message sert à l'information seulement et n'aura pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
Subject: NAR assembly
Date: Thu, 29 Oct 2009 11:30:47 -0500
From: dajacob...@lifetouch.com
To: users@maven.apache.org
I am now getting into building the assembly portion of this. I don't
think the nar is getting looked up correctly. The nar is placed in the
system as a x86-Windows-g++-jni.jar, but the assembly plugin is looking
for x86-Windows-jni.jar. Also, even though I am explicitly setting the
classifier, the output references x86-Windows-msvc. I am trying to
figure out how to get it so I can run the plugin in debug mode in
Eclipse so I can help unravel this.
Damon
[INFO] snapshot com.lifetouch.utility:ioutilities:1.1.0-SNAPSHOT:
checking for updates from snapshots
[INFO] [nar:nar-download {execution: default}]
[INFO] Using AOL: x86-Windows-msvc
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] nar not found
com.lifetouch.utility:ImagenomicPortraiturePluginDLL:nar:x86-Windows-jni
:0.0.1-SNAPSHOT
Embedded error: Unable to download the artifact from any repository
POM.XML
plugin
artifactIdmaven-assembly-plugin/artifactId
configuration
descriptors
descriptorsrc/main/assembly/assembly.xml/descriptor
/descriptors
/configuration
/plugin
plugin
artifactIdmaven-nar-plugin/artifactId
configuration
classifiers
classifierx86-Windows-g++/classifier
/classifiers
/configuration
executions
execution
goals
goalnar-download/goal
goalnar-unpack/goal
goalnar-assembly/goal
/goals
/execution
/executions
/plugin
ASSEBMLY.XML
assembly
iddistribution/id
formats
!-- can't seem to find reference to dir, which is what I
really want, guess I will unzip manually --
formatzip/format
/formats
includeBaseDirectoryfalse/includeBaseDirectory
dependencySets
dependencySet
unpackfalse/unpack
scoperuntime/scope
/dependencySet
/dependencySets
fileSets
fileSet
directorytarget/nar/lib/x86-Windows-g++/directory
outputDirectorylib/outputDirectory
includes
include*/include
/includes
/fileSet
fileSet
includes
include${project.basedir}/README*/include
include${project.basedir}/LICENSE*/include
include${project.basedir}/NOTICE*/include
/includes
/fileSet
fileSet
directory${project.build.directory}/directory
includes
include*.jar/include
/includes
/fileSet
/fileSets
/assembly
__
This email has been scanned by the MessageLabs Email Security System.
Plugin Listing
The Maven Dependency Plugin has dependency:list which lists out all the dependency versions being used. Is there a similar listing to display all build plugin versions? Is there a similar listing to display all reporting plugin versions? Paul - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Plugin Listing
there is some help with versions:display-plugin-updates... may not give you everything you are after, but at least some of what you want 2009/10/29 Paul Benedict pbened...@apache.org: The Maven Dependency Plugin has dependency:list which lists out all the dependency versions being used. Is there a similar listing to display all build plugin versions? Is there a similar listing to display all reporting plugin versions? Paul - 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: Plugin Listing
The enforcer requirePluginVersions rule will do it, and make sure you've locked them all down at the same time as a bonus ;-) On Thu, Oct 29, 2009 at 5:04 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: there is some help with versions:display-plugin-updates... may not give you everything you are after, but at least some of what you want 2009/10/29 Paul Benedict pbened...@apache.org: The Maven Dependency Plugin has dependency:list which lists out all the dependency versions being used. Is there a similar listing to display all build plugin versions? Is there a similar listing to display all reporting plugin versions? Paul - 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
Any maven project using DITA Open Toolkit out there?
Hi, I just hacked up a maven plugin called dita-maven-plugin which is just a wrapper of DITA Open Toolkit's Java command line The site is at http://mojo.codehaus.org/dita-maven-plugin Feedback are every welcome Thanks -Dan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: tracking down jetty/tomcat dependencies
On Fri, Oct 30, 2009 at 6:45 AM, Benson Margulies bimargul...@gmail.comwrote: I've got code that works fine when run as a pojo and fails when run in a webapp, either via tomcat:run or jetty:run. I suspect, because I can't think of anything else, that there is detritus in the 'system' classpaths of these containers. However, mvn dependency:tree does not tell me much about the maven-jetty-plugin. Neither does dependency:resolve-plugins. Is there some way to get a clearer view of this question? What is the mode of failure? Brett
Using Ivy repository in Maven
Hi all, I'm quite new to Maven. Currently I use ant to build my java applications and use Ivy as dependency management tool. I'm keeping all by dependency jars in svn and use ant+ivy to get them when I build my application. Now I'm planning to move to maven and I wanted to have a local repository for maven. In maven is there a way which i can directly access the jars I currently have in svn, or is there a way to import them to maven repository? Since I've quite a lot of jars in svn (currently using with ant + ivy) it is not easy to do that manually. Thanks and regards, sandarenu. -- View this message in context: http://old.nabble.com/Using-Ivy-repository-in-Maven-tp26124183p26124183.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
