release:prepare and bazaar
Hi I'm trying to do a release using maven and bazaar, and i get the following error: [INFO] Tagging release with the label drizzle-jdbc-0.1... [INFO] [ERROR] BUILD ERROR [INFO] [INFO] An error is occurred in the tag process: No such command 'tag'. Are there any workarounds for this? Can I force release:prepare not to tag? /Marcus
Re: Maven sites and APT
On the Doxia level you can split apt files just like described. On the Maven level, the site plugin always includes files as separate documents, as specified in site.xml. So I guess it's currently not possible to use this feature in Maven. HTH, -Lukas Bryon Jacob wrote: Quick question that I've not been able to find an answer for online... The guide to the APT format at http://maven.apache.org/doxia/references/apt-format.html says: A short APT document is contained in a single text file. A longer document may be contained in a ordered list of text files. For instance, first text file contains section 1, second text file contains section 2, and so on. How does one specify a file to be split into multiple parts as described? thanks! - Bryon - 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: release:perform of an EAR gives error with maven-source-plugin:2.1
On 30 Apr 2009, Grant Rettke wrote: Does the workaround on that page work? Which workaround? Do you mean the patch attached to the MSOURCES-44 issue? I didn't test it but I had a look at the patch and I would assume it would work. - martin signature.asc Description: PGP signature
Re: Multimodule release with same version for everything and dependency version update
Well, not so good in the end. For the record, here is a summary of the
things I've discovered so far (I guess some could be listed in the FAQ,
btw). These come from my personal testing. So, if some of the statements
below are know in your opinion, please let me know.
Note I only tested my use case: i.e. same version for the whole multimodule
project, with sibling hierarchy, i.e.:
* parent-pom (referencing the two submodules with ../projectA and
../projectB)
* projectA (with relativePath to ../parent-pom)
* projectB
Results:
* release:prepare won't be able to to complete successfullu without
-DpreparationGoals=clean install. In fact, contrary to classical mvn
clean verify on the multimodule hierarchy, in the context of
release:prepare it seems unable to find it in the reactor. Btw, I found some
blog about this on the web.
* the release-plugin does not support non hierarchical multi-module project
like described above. Actually, it will only tag the project root, and not
be able to find the sub-modules tags when trying to release:perform. I
perfectly understand the complexity behind this (how to find the tagBase of
the subModule if not tagged in the same place...). But I just think this
limitation should be reminded more clearly in the project FAQ. Maybe it
should be (if not already) said somewhere in the doc that non-hierarchical
multimodule project can be problematic, if not unfeasible, to release via
the release-plugin.
* Apart from this blocker limitation, auto-versioning the whole tree seems
to work fine using ${project.version} and -DautoVersionSubmodules=true.
To conclude, I think I'm going to refactor my project so that it becomes a
real hierarchy to be able to use the maven-release-plugin in its supported
use case.
If you have any advice or thought about this subject, I'll be glad to hear
about it.
Cheers.
2009/4/30 Baptiste MATHUS m...@batmat.net
Pfff, forget this mail. Just noticed I was actually too blind to see the
error was not the one I wanted to read...
Seems like my brilliant idea in the end of the previous mail is already
what is done...
Thanks anyway and sorry for the noise :-).
2009/4/30 Baptiste MATHUS m...@batmat.net
Yes, I already tried it, but the release-plugin resolves the current
revision before release which is still a SNAPSHOT one. So it aborts the
release saying there's a snapshot dependency to be resolved before...
$ mvn --batch-mode release:clean release:prepare -DdryRun=true
-DautoVersionSubModules=true -DreleaseVersion=2.3.0 -
DdevelopmentVersion=2.4.0-SNAPSHOT
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Pom parent des projets socle
[INFO] Socle Technique (projectA)
[INFO] Socle Fonctionnel (projectB)
[INFO] Searching repository for plugin with prefix: 'release'.
[INFO]
[INFO] Building POM parent des projets MM
[INFO]task-segment: [release:clean, release:prepare]
(aggregator-style)
[INFO]
[INFO] [release:clean]
[INFO] Cleaning up after release...
[INFO] [release:prepare]
[INFO] Verifying that there are no local modifications...
[INFO] Executing: cmd.exe /X /C svn --non-interactive status
[INFO] Working directory: C:\tests\refacto-multimodules-socle\our-parent
[INFO] Checking dependencies and plugins for snapshots ...
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Can't release project due to non released dependencies :
fr.ourcompany:foundation.test:jar:2.3.0-SNAPSHOT:test
in project 'Socle Fonctionnel'
(fr.ourcompany:socle-fonctionnel:bundle:2.3.0-SNAPSHOT)
I think the release-plugin should try to detect dependencies that matches
those currrently in the reactor, and use the releaseVersion if the
autoVersionSubModules was given. Seems conceptually feasible. What do you
think?
Cheers.
2009/4/30 Jasper de Vries lit...@gmail.com
if you make project B dependent on project A with a version of
${project.version} it will inherit the version of the parent pom (just
like
the build for B does).
On Thu, Apr 30, 2009 at 5:05 PM, Baptiste MATHUS m...@batmat.net wrote:
Hi all,
I'm currently stuck in a problem of chicken and egg problem. I already
read
and thought a lot about it. But as I don't think I'll find the best way
alone, I'm trying the list.
I've read again the following recent thread
http://www.nabble.com/Version-Number-Inheritance-td23304326.html but
if I
read it correctly it doesn't speak about the problem I'm encountering :
managing the dependency versions. Obviously speaking about the
dependencies
included in the release being done. I hope I'm being clear :-/.
Let's explain a bit more the problem with a description and some
excerpt of
my poms. I want to
ScpWagon for 'httpHeaders' deploy 2.1.0 (macosx)
I am working on a MacOSX machine. I downloaded the 2.1.0 maven release. When I ran the 'deploy' goal it on some projects that have been running smoothly on 2.0.10 I encountered the following problem: Unable to apply wagon configuration. Cannot find setter nor field in org.apache.maven.wagon.providers.ssh.jsch.ScpWagon for 'httpHeaders' There seemed to be some relationship between some of the dependencies in the project and the failing behavior. Any ideas?
Reporting Question
It's established that links won't work for deployment of multi-module
sites [1], i.e. links don't work for
% mvn site site:deploy
But I can get
% mvn site:stage-deploy
to deploy a 'staged' site to a remote URL [even the same URL specified
by ${project.distributionManagement.site.url}] and the site links
*work*.
First question ...
If links can be made to work using 'site:stage-deploy', why can't they
be made to work for 'site:deploy'?
Second Question ...
If I configure an execution of the 'stage-deploy' goal with
stagingSiteURL${project.distributionManagement.site.url}/stagingSiteU
RL
I'm prompted for an LDAP password at multiple steps during the
deployment. This does not occur when using the simple 'deploy' goal, by
virtue of a settings.xml server element with username and password
defined for the target host.
Why is this?
[1] http://maven.apache.org/plugins/maven-site-plugin/ (multiple
references)
Thanks.
Brad
Automagically update scm tag
Hi all, I'm looking for a simple a quick way to update my scm tags. I'm currently refactoring my projects, and I find it cumbersome to manually update ths scm tag to the new although the information is already present in the svn metadata. I took a quick look at scm:*** goals but can't find the one that fits my need corresponding (moreover I think this plugin is more designed to be used as a dependency to front-end plugin, so there's not a lot documentation for each goals :)). What I'd like is a goal that would retrieved the svn info . command output and update the scm *connection tags in the pom. Does this goal already exist or should I file an improvement request about it? Thanks a lot. Cheers. -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: How to specify SCM username/password for release plugin?
Hi, In the documentation of the mojo (btw, you didn't say which goal you were speaking) of the release:prepare for example: http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html username/password. Cheers. 2009/5/1 David Hoffer dhoff...@gmail.com How can I specify the username/password to be used by the release plugin in the settings.xml file (or other system approach)? Normally this is set in the settings.xml and refereed to elsewhere by it's id but how is this refereed by the SCM? -Dave -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Cannot find Plexus container
I am trying to create an AndroMDA application using Maven. Have installed Maven (2.0.4) and also installed AndroMDA plugin. But when i execute andromdapp:generate i get the following error: D:\MyProjectmvn --version Maven version: 2.0.4 D:\MyProjectmvn andromdapp:generate [INFO] Scanning for projects... [INFO] - --- [INFO] Building Maven Default Project [INFO] task-segment: [andromdapp:generate] (aggregator-style) [INFO] - --- [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager executing goal 'org.andromda.maven.p lugins:andromdapp-maven-plugin:3.2:generate': Cannot find Plexus container for p lugin: org.andromda.maven.plugins:andromdapp-maven-plugin [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Tue Apr 28 13:32:34 IST 2009 [INFO] Final Memory: 2M/4M [INFO] = Stack trace with -e and -X options: == D:\MyProjectmvn andromdapp:generate -e -X + Error stacktraces are turned on. Maven version: 2.0.4 [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settin gs\aagga\.m2\plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'D:\apps\maven-2.0.4\c onf\plugin-registry.xml' [INFO] Scanning for projects... [INFO] - --- [INFO] Building Maven Default Project [INFO] task-segment: [andromdapp:generate] (aggregator-style) [INFO] - --- [DEBUG] org.apache.maven:super-pom:jar:2.0 (selected for null) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager executing goal 'org.andromda.maven.p lugins:andromdapp-maven-plugin:3.2:generate': Cannot find Plexus container for p lugin: org.andromda.maven.plugins:andromdapp-maven-plugin [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the pl ugin manager executing goal 'org.andromda.maven.plugins:andromdapp-maven-plugin: 3.2:generate': Cannot find Plexus container for plugin: org.andromda.maven.plugi ns:andromdapp-maven-plugin at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:538) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone Goal(DefaultLifecycleExecutor.java:488) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:458) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:219) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.PluginManagerException: Cannot find Plexus co ntainer for plugin: org.andromda.maven.plugins:andromdapp-maven-plugin at org.apache.maven.plugin.DefaultPluginManager.getPluginContainer(Defau ltPluginManager.java:499) at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(Defaul tPluginManager.java:514) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:390) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:534) ... 16 more [INFO]
Automagically update scm tag
Hi all, I'm looking for a simple a quick way to update my scm tags. I'm currently refactoring my projects, and I find it cumbersome to manually update ths scm tag to the new although the information is already present in the svn metadata. I took a quick look at scm:*** goals but can't find the one that fits my need corresponding (moreover I think this plugin is more designed to be used as a dependency to front-end plugin, so there's not a lot documentation for each goals :)). What I'd like is a goal that would retrieved the svn info . command output and update the scm *connection tags in the pom. Does this goal already exist or should I file an improvement request about it? Thanks a lot. Cheers. -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Error transferring file: repo1.maven.org, Repository 'central' will be blacklisted
Hi, I'm doing apache servicemix tutorials (tutorial 3: Camel) using maven, when I run mvn archetype:create I get a message saying that an error occurred transferring data from repo1.maven.org I have a working internet connection (through which I'm writing this email), and I'm able to open without any problem the site repo1.maven.org from Firefox (through which I'm writing this email, too). Seems that maven is not able to use the net, but I don't see why: in past runs it was able to connect. Is that a settings problem? Thanks in advance, Andrea and...@martin:~/Programmi/apache-servicemix-3.3/tutorials/3_camel$ mvn --version Apache Maven 2.1.0 (r755702; 2009-03-18 20:10:27+0100) Java version: 1.6.0_13 Java home: /home/andrea/Programmi/jdk1.6.0_13/jre Default locale: it_IT, platform encoding: UTF-8 OS name: linux version: 2.6.28-11-generic arch: i386 Family: unix and...@martin:~/Programmi/apache-servicemix-3.3/tutorials/3_camel$ mvn archetype:create -e -U -DarchetypeArtifactId=servicemix-camel-service-unit -DarchetypeGroupId=org.apache.servicemix.tooling -DartifactId=tutorial-camel-su + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] org.apache.maven.plugins: checking for updates from central [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be retrieved from repository: central due to an error: Error transferring file: repo1.maven.org [INFO] Repository 'central' will be blacklisted [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or no valid version could be found [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or no valid version could be found at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1546) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1786) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:446) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:176) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(laand...@martin:~/Programmi/apache-servicemix-3.3/tutorials/3_camel$ mvn archetype:create -DarchetypeArtifactId=servicemix-camel-service-unit -DarchetypeGroupId=org.apache.servicemix.tooling -DartifactId=tutorial-camel-su [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] org.apache.maven.plugins: checking for updates from central [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be retrieved from repository: central due to an error: Error transferring file: repo1.maven.org [INFO] Repository 'central' will be blacklisted [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or no valid version could be found [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Mon May 04 12:19:27 CEST 2009 [INFO] Final Memory: 1M/65M [INFO] uncher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.version.PluginVersionNotFoundException: The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or no valid version could be found at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:229) at
Re: ScpWagon for 'httpHeaders' deploy 2.1.0 (macosx)
I saw this issue online [1] but haven't had a chance to investigate yet. Could you report it in JIRA, and post the contents of your distributionManagement and build extensions? Thanks, Brett [1] http://johnsjavapda.blogspot.com/2009/04/210-is-not-2010-maven-blues.html On 02/05/2009, at 3:36 AM, John Kroubalkian wrote: I am working on a MacOSX machine. I downloaded the 2.1.0 maven release. When I ran the 'deploy' goal it on some projects that have been running smoothly on 2.0.10 I encountered the following problem: Unable to apply wagon configuration. Cannot find setter nor field in org.apache.maven.wagon.providers.ssh.jsch.ScpWagon for 'httpHeaders' There seemed to be some relationship between some of the dependencies in the project and the failing behavior. Any ideas? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to specify SCM username/password for release plugin?
(with appropriate substitutions of course) In our topmost pom for the project we use: scm developerConnectionscm:svn:https://svnhost/svnrepo/trunk/developerConnection /scm and in the settings.xml (of those allowed to do releases) we put both server entries: servers server idlibs-releases/id usernamethereleaseuser/username passwordthereleasepassword/password /server server idlibs-snapshots/id usernamethedeveloperuser/username passwordthedeveloperpassword/password /server /servers Regards, Gord Cody On Mon, May 4, 2009 at 5:46 AM, Baptiste MATHUS m...@batmat.net wrote: Hi, In the documentation of the mojo (btw, you didn't say which goal you were speaking) of the release:prepare for example: http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html username/password. Cheers. 2009/5/1 David Hoffer dhoff...@gmail.com How can I specify the username/password to be used by the release plugin in the settings.xml file (or other system approach)? Normally this is set in the settings.xml and refereed to elsewhere by it's id but how is this refereed by the SCM? -Dave -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to specify SCM username/password for release plugin?
Does this support encryption? We don't want passwords in plan text. We really don't want names/passwords in the pom as those are global values, we really want server names/passwords encrypted and in the settings.xml or other system location. we run release:prepare followed by release:perform -Dave On Mon, May 4, 2009 at 3:46 AM, Baptiste MATHUS m...@batmat.net wrote: Hi, In the documentation of the mojo (btw, you didn't say which goal you were speaking) of the release:prepare for example: http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html username/password. Cheers. 2009/5/1 David Hoffer dhoff...@gmail.com How can I specify the username/password to be used by the release plugin in the settings.xml file (or other system approach)? Normally this is set in the settings.xml and refereed to elsewhere by it's id but how is this refereed by the SCM? -Dave -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: How to specify SCM username/password for release plugin?
How is either server id tied to the SCM? We too have server id/s but these are used for artifact deployment login not SCM login. How can I use these for SCM login? -Dave On Mon, May 4, 2009 at 6:22 AM, Gordon Cody gc...@zafinlabs.com wrote: (with appropriate substitutions of course) In our topmost pom for the project we use: scm developerConnectionscm:svn:https://svnhost/svnrepo/trunk /developerConnection /scm and in the settings.xml (of those allowed to do releases) we put both server entries: servers server idlibs-releases/id usernamethereleaseuser/username passwordthereleasepassword/password /server server idlibs-snapshots/id usernamethedeveloperuser/username passwordthedeveloperpassword/password /server /servers Regards, Gord Cody On Mon, May 4, 2009 at 5:46 AM, Baptiste MATHUS m...@batmat.net wrote: Hi, In the documentation of the mojo (btw, you didn't say which goal you were speaking) of the release:prepare for example: http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html username/password. Cheers. 2009/5/1 David Hoffer dhoff...@gmail.com How can I specify the username/password to be used by the release plugin in the settings.xml file (or other system approach)? Normally this is set in the settings.xml and refereed to elsewhere by it's id but how is this refereed by the SCM? -Dave -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to specify SCM username/password for release plugin?
You want to have a look at this:
http://maven.apache.org/guides/mini/guide-encryption.html
However, this is only available since 2.1.
Btw, we use user/password. Settings.xml is shared by everybody, we just use
something like ${env.m2DeployUser}/${env.m2DeployPwd} and then ask the
developers who have deployment account to specify value for the
corresponding environment variable with their own account credentials. This
way, they're the only one to know their user/pwd. The Settings.xml doesn't
convey any.
Cheers.
2009/5/4 David Hoffer dhoff...@gmail.com
Does this support encryption? We don't want passwords in plan text. We
really don't want names/passwords in the pom as those are global values, we
really want server names/passwords encrypted and in the settings.xml or
other system location.
we run release:prepare followed by release:perform
-Dave
On Mon, May 4, 2009 at 3:46 AM, Baptiste MATHUS m...@batmat.net wrote:
Hi,
In the documentation of the mojo (btw, you didn't say which goal you were
speaking) of the release:prepare for example:
http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html
username/password.
Cheers.
2009/5/1 David Hoffer dhoff...@gmail.com
How can I specify the username/password to be used by the release
plugin
in
the settings.xml file (or other system approach)? Normally this is set
in
the settings.xml and refereed to elsewhere by it's id but how is this
refereed by the SCM?
-Dave
--
Baptiste Batmat MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
--
Baptiste Batmat MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
Re: Error transferring file: repo1.maven.org, Repository 'central' will be blacklisted
Have you enabled a proxy inside your browser through which you connect to the internet? If so, you have to tell maven about this proxy by enabling it inside the settings.xml. [1] [1] http://maven.apache.org/ref/2.0.7/maven-settings/settings.html#class_proxy Hth, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Mon, May 4, 2009 at 12:36 PM, Andrea Libero Valori andrealibero.val...@gmail.com wrote: Hi, I'm doing apache servicemix tutorials (tutorial 3: Camel) using maven, when I run mvn archetype:create I get a message saying that an error occurred transferring data from repo1.maven.org I have a working internet connection (through which I'm writing this email), and I'm able to open without any problem the site repo1.maven.org from Firefox (through which I'm writing this email, too). Seems that maven is not able to use the net, but I don't see why: in past runs it was able to connect. Is that a settings problem? Thanks in advance, Andrea and...@martin:~/Programmi/apache-servicemix-3.3/tutorials/3_camel$ mvn --version Apache Maven 2.1.0 (r755702; 2009-03-18 20:10:27+0100) Java version: 1.6.0_13 Java home: /home/andrea/Programmi/jdk1.6.0_13/jre Default locale: it_IT, platform encoding: UTF-8 OS name: linux version: 2.6.28-11-generic arch: i386 Family: unix and...@martin:~/Programmi/apache-servicemix-3.3/tutorials/3_camel$ mvn archetype:create -e -U -DarchetypeArtifactId=servicemix-camel-service-unit -DarchetypeGroupId=org.apache.servicemix.tooling -DartifactId=tutorial-camel-su + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] org.apache.maven.plugins: checking for updates from central [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be retrieved from repository: central due to an error: Error transferring file: repo1.maven.org [INFO] Repository 'central' will be blacklisted [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or no valid version could be found [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or no valid version could be found at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1546) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1786) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:446) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:176) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(laand...@martin:~/Programmi/apache-servicemix-3.3/tutorials/3_camel$ mvn archetype:create -DarchetypeArtifactId=servicemix-camel-service-unit -DarchetypeGroupId=org.apache.servicemix.tooling -DartifactId=tutorial-camel-su [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] org.apache.maven.plugins: checking for updates from central [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be retrieved from repository: central due to an error: Error transferring file: repo1.maven.org [INFO] Repository 'central' will be blacklisted [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or no valid version could be found [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Mon May 04 12:19:27 CEST 2009 [INFO] Final Memory: 1M/65M [INFO] uncher.java:315) at
Re: release:perform of an EAR gives error with maven-source-plugin:2.1
On Mon, May 4, 2009 at 2:01 AM, Martin Höller mar...@xss.co.at wrote: On 30 Apr 2009, Grant Rettke wrote: Does the workaround on that page work? Which workaround? Do you mean the patch attached to the MSOURCES-44 issue? I didn't test it but I had a look at the patch and I would assume it would work. Yes is what I meant. I was wondering if it worked; nothing more. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Reporting Question
it seems that project.distributionManagement.site.url is a production site
guarded by LDAP authentication
at the very min you will need these details from LDAP admin
hostname
port
authdn e.g. uid=admin,ou=system
and passwd
from LDAP admin
I found this tutorial of LDAP plugin helpful
http://ldap-plugin.btmatthews.com/usage.html
Martin
__
Disclaimer and Confidentiality/Verzicht und Vertraulichkeitanmerkung / Note de
déni et de confidentialité
This message is confidential. If you should not be the intended receiver, then
we ask politely to report. Each unauthorized forwarding or manufacturing of a
copy is inadmissible. This message serves only for the exchange of information
and has no legal binding effect. Due to the easy manipulation of emails we
cannot take responsibility over the the contents.
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: Reporting Question
Date: Fri, 1 May 2009 09:43:59 -0500
From: brad.har...@fiserv.com
To: users@maven.apache.org
It's established that links won't work for deployment of multi-module
sites [1], i.e. links don't work for
% mvn site site:deploy
But I can get
% mvn site:stage-deploy
to deploy a 'staged' site to a remote URL [even the same URL specified
by ${project.distributionManagement.site.url}] and the site links
*work*.
First question ...
If links can be made to work using 'site:stage-deploy', why can't they
be made to work for 'site:deploy'?
Second Question ...
If I configure an execution of the 'stage-deploy' goal with
stagingSiteURL${project.distributionManagement.site.url}/stagingSiteU
RL
I'm prompted for an LDAP password at multiple steps during the
deployment. This does not occur when using the simple 'deploy' goal, by
virtue of a settings.xml server element with username and password
defined for the target host.
Why is this?
[1] http://maven.apache.org/plugins/maven-site-plugin/ (multiple
references)
Thanks.
Brad
_
Hotmail® has ever-growing storage! Don’t worry about storage limits.
http://windowslive.com/Tutorial/Hotmail/Storage?ocid=TXT_TAGLM_WL_HM_Tutorial_Storage1_052009
Managing Modified Dependencies
The situation: * Company finds a show stopping bug in dependency Foo * Company can not wait for the owner of Foo to fix it * Company branches the source code locally and applies patch * Company now needs to maintained a modified third party dependency Currently some crazy system of relative paths and fake version numbers is being used to resolve the modified dependencies. However, this is obviously an eye soar sore and is cluttering up our source repository. What are some solutions for ensuring that changes don't get overwritten and our repository stays clean? Any suggestion will be welcomed! I appreciate your time, thank you at least for that :-), Daniel. -- View this message in context: http://www.nabble.com/Managing-Modified-Dependencies-tp23371539p23371539.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: Managing Modified Dependencies
On Mon, May 4, 2009 at 1:01 PM, Nick Stolwijk nick.stolw...@gmail.comwrote: Normally I just check out the source, apply my patches, update the deploymentManament section to point to our inhouse repository, update the version to x.y.z-companyname-1 and do a maven deploy. Then update the documentation to mention which revision you checked out (preferably a tag) and for which issues you have applied a patch, so that the build is reproducible. That'd would be roughly similar to how I would typically handle it. If the changes are significant, I might also check in to local source control. In all scenarios, I'd be hoping to get back on a public version ASAP. - Geoffrey -- Geoffrey Wiseman http://www.geoffreywiseman.ca/
RE: 2 modules with same source
Hi, One of the modues neeed to exposed over the net wheres others should't Regards - Origial Message - From: Martin Gainty mgai...@hotmail.com To: users@maven.apache.org Sent: Mon, 4 May 2009 05:28:53 +0530 (IST) Subject: RE: 2 modules with same source One war supported by multiple EJBs is easier to maintain and accomplishes the objective of naming, assembling and configuring a web which accomplishes one purpose Could you elaborate on the objective your requirement states for the need for 2 completely separate WARS in 1 ear? Thanks, Martin Gainty __ Disclaimer and Confidentiality/Verzicht und Vertraulichkeitanmerkung / Note de déni et de confidentialité This message is confidential. If you should not be the intended receiver, then we ask politely to report. Each unauthorized forwarding or manufacturing of a copy is inadmissible. This message serves only for the exchange of information and has no legal binding effect. Due to the easy manipulation of emails we cannot take responsibility over the the contents. 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. Date: Sun, 3 May 2009 23:24:51 +0530 From: neptune_pl...@indiatimes.com To: users@maven.apache.org Subject: 2 modules with same source Hi, I have 2 web modules in my ear. but there isn only 1 set of src files i need to maintain. As far as the logic for maintainging 2 modules,its more from a business reqment. So is it possible to maintain src files in module and utilize the same in another module during any checkout/update Regards -- Exclusive spy camera shots of the Tata Nano only on ZigWheels.com http://www.zigwheels.com/tata-nano/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org _ Hotmail® has a new way to see what's up with your friends. http://windowslive.com/Tutorial/Hotmail/WhatsNew?ocid=TXT_TAGLM_WL_HM_Tutorial_WhatsNew1_052009 -- Exclusive spy camera shots of the Tata Nano only on ZigWheels.com http://www.zigwheels.com/tata-nano/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven release plugin issue
Hi,
I am running maven release plugin by:
mvn -f pom.xml -Pabc.debug.release --batch-mode -Dtag=REL1.5-TEST
-DtagBase=https://abcsvn001.na.abcglobal.com/abc_repos/T3/tags;
-DreleaseVersion=1.5 -DdevelopmentVersion=1.6-SNAPSHOT release:prepare
And I get this build error.
[INFO] [INFO] An Ant BuildException has occured: The following error
occurred wh
ile executing this line:
[INFO]
C:\mvn_rel\int_002_dev_test\services-api\abc-interface-api\xsd-extract.xm
l:19: Error while expanding C:\Documents and
Settings\huser\.m2\repository\co
m\abc\t3\abc-websvc-api\1.5\abc-websvc-api-1.5.jar
[INFO] java.io.FileNotFoundException: C:\Documents and
Settings\huser\.m2\rep
ository\com\abc\t3\abc-websvc-api\1.5\abc-websvc-api-1.5.jar (The system
cannot
find the path specified)
I do not get this error if I do not use the release plugin i.e.
mvn -f pom.xml -Pabc.debug.release clean install deploy
In my xsd-extract.xml, I have an environment variable $verinfo which
unjar
src=${env.M2_REPO}/com/abc/t3/abc-websvc-api/${verinfo}/abc-websvc-api-${verinfo}.jar
gets its value defined in abc-interface-api
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
executions
execution
idextract-xsds/id
phaseinitialize/phase
configuration
tasks
property name=verinfo value=${project.parent.version} /
echo message=My dependency name: ${verinfo} /
ant antfile=${basedir}/xsd-extract.xml
target name=retrieve-xsds /
/ant
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
/plugin
Why is abc-websvc-api-1.5.jar being called before it is deployed in .m2 ?
This jar does get generated in abc-interface-api\target. But it does not get
deployed in .m2
Any ideas ?
thanks,
--
View this message in context:
http://www.nabble.com/maven-release-plugin-issue-tp23375978p23375978.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 release plugin issue
ugh!
that sounds hacky hacky hack
you probably should try having the dependency plugin unpack for you
-Stephen
On 04/05/2009, huser mpinj...@atxg.com wrote:
Hi,
I am running maven release plugin by:
mvn -f pom.xml -Pabc.debug.release --batch-mode -Dtag=REL1.5-TEST
-DtagBase=https://abcsvn001.na.abcglobal.com/abc_repos/T3/tags;
-DreleaseVersion=1.5 -DdevelopmentVersion=1.6-SNAPSHOT release:prepare
And I get this build error.
[INFO] [INFO] An Ant BuildException has occured: The following error
occurred wh
ile executing this line:
[INFO]
C:\mvn_rel\int_002_dev_test\services-api\abc-interface-api\xsd-extract.xm
l:19: Error while expanding C:\Documents and
Settings\huser\.m2\repository\co
m\abc\t3\abc-websvc-api\1.5\abc-websvc-api-1.5.jar
[INFO] java.io.FileNotFoundException: C:\Documents and
Settings\huser\.m2\rep
ository\com\abc\t3\abc-websvc-api\1.5\abc-websvc-api-1.5.jar (The system
cannot
find the path specified)
I do not get this error if I do not use the release plugin i.e.
mvn -f pom.xml -Pabc.debug.release clean install deploy
In my xsd-extract.xml, I have an environment variable $verinfo which
unjar
src=${env.M2_REPO}/com/abc/t3/abc-websvc-api/${verinfo}/abc-websvc-api-${verinfo}.jar
gets its value defined in abc-interface-api
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
executions
execution
idextract-xsds/id
phaseinitialize/phase
configuration
tasks
property name=verinfo value=${project.parent.version} /
echo message=My dependency name: ${verinfo} /
ant antfile=${basedir}/xsd-extract.xml
target name=retrieve-xsds /
/ant
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
/plugin
Why is abc-websvc-api-1.5.jar being called before it is deployed in .m2 ?
This jar does get generated in abc-interface-api\target. But it does not get
deployed in .m2
Any ideas ?
thanks,
--
View this message in context:
http://www.nabble.com/maven-release-plugin-issue-tp23375978p23375978.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
Looking for plugin to examine surefire results in post-integration-test phase
I am using the surefire plugin to run integration tests during the integration-test phase. To ensure the test environment is properly torn down in the post-integration-test phase I have set testFailureIgnore=true within the surefire plugin configuration. I would like to find a plugin I can run during the post-integration-test phase which will examine the test result XML files and fail the build if any test failures were encountered. What plugin should I use to look for test failures in the test report files and fail the build in a later phase than the one the surefire plugin runs in? CONFIDENTIALITY NOTICE: This message is intended only for the use and review of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message solely to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify sender immediately by telephone or return email. Thank you. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven release plugin issue
I am fairly new to maven. So I guess I need a plugin to copy the
abc-interface-api.jar to my local repository ? Are you suggesting I do this
by dependency plugin. I tried adding this.
Basically, abc-interface-api-$project.parent.version} should get copied to
local .m2 repository under com/abc/t3/abc-interface=api/1.6
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
executions
execution
idcopy/id
phasepackage/phase
goals
goalcopy/goal
/goals
configuration
artifactItems
artifactItem
groupIdcom.abc.t3/groupId
artifactIdabc-interface-api/artifactId
version${project.parent.version}/version
typejar/type
overWritetrue/overWrite
outputDirectory${env.M2_REPO}/com/abc/t3/outputDirectory
destFileNameabc-interface-api-${project.parent.version}.jar/destFileName
/artifactItem
/artifactItems
!-- other configurations here --
/configuration
/execution
/executions
/plugin
but, then I get this error:
[INFO] [ERROR] BUILD ERROR
[INFO] [INFO]
--
--
[INFO] [INFO] Unable to find artifact.
[INFO]
[INFO] Embedded error: Unable to download the artifact from any repository
[INFO]
[INFO] Try downloading the file manually from the project website.
[INFO]
[INFO] Then, install it using the command:
[INFO] mvn install:install-file -DgroupId=com.abc.t3
-DartifactId=abc-inter
face-api -Dversion=1.6 -Dpackaging=jar -Dfile=/path/to/file
[INFO]
[INFO] Alternatively, if you host your own repository you can deploy the
file th
ere:
[INFO] mvn deploy:deploy-file -DgroupId=com.abc.t3
-DartifactId=abc-interfa
ce-api -Dversion=1.6 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
-Dreposito
ryId=[id]
[INFO]
[INFO]
[INFO] com.abc.t3:abc-interface-api:jar:1.6
[INFO]
[INFO] from the specified remote repositories:
[INFO] nexus
(http://abcsvn001.na.abcglobal.com:8081/nexus/content/groups/publi
c),
[INFO] snapshots
(http://abcsvn001.na.abcglobal.com:8081/nexus/content/reposito
ries/snapshots)
[INFO]
[INFO] [INFO]
--
Stephen Connolly-2 wrote:
ugh!
that sounds hacky hacky hack
you probably should try having the dependency plugin unpack for you
-Stephen
On 04/05/2009, huser mpinj...@atxg.com wrote:
Hi,
I am running maven release plugin by:
mvn -f pom.xml -Pabc.debug.release --batch-mode -Dtag=REL1.5-TEST
-DtagBase=https://abcsvn001.na.abcglobal.com/abc_repos/T3/tags;
-DreleaseVersion=1.5 -DdevelopmentVersion=1.6-SNAPSHOT release:prepare
And I get this build error.
[INFO] [INFO] An Ant BuildException has occured: The following error
occurred wh
ile executing this line:
[INFO]
C:\mvn_rel\int_002_dev_test\services-api\abc-interface-api\xsd-extract.xm
l:19: Error while expanding C:\Documents and
Settings\huser\.m2\repository\co
m\abc\t3\abc-websvc-api\1.5\abc-websvc-api-1.5.jar
[INFO] java.io.FileNotFoundException: C:\Documents and
Settings\huser\.m2\rep
ository\com\abc\t3\abc-websvc-api\1.5\abc-websvc-api-1.5.jar (The system
cannot
find the path specified)
I do not get this error if I do not use the release plugin i.e.
mvn -f pom.xml -Pabc.debug.release clean install deploy
In my xsd-extract.xml, I have an environment variable $verinfo which
unjar
src=${env.M2_REPO}/com/abc/t3/abc-websvc-api/${verinfo}/abc-websvc-api-${verinfo}.jar
gets its value defined in abc-interface-api
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
executions
execution
idextract-xsds/id
phaseinitialize/phase
configuration
tasks
property name=verinfo value=${project.parent.version} /
echo message=My dependency name: ${verinfo} /
ant antfile=${basedir}/xsd-extract.xml
target name=retrieve-xsds /
/ant
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
/plugin
Why is abc-websvc-api-1.5.jar being called before it is deployed in .m2 ?
This jar does get generated in abc-interface-api\target. But it does not
get
deployed in .m2
Any ideas ?
[PLEASE TEST] Maven 2.2.0-RC2
Hi again, After finding and cleaning up some code that seems to be tainted during some of our efforts at generifying the codebase, we've respun a new release candidate. If you have time, please give it a whirl: https://repository.apache.org/content/repositories/maven-staging-010/org/apache/maven/apache-maven/2.2.0-RC2/ Remember, if you have any problems, report them to: http://jira.codehaus.org/browse/MNG with Affects-Version: 2.2.0 ...then, please reply to this thread to let me know about the issue! :-) Thanks for testing! -john - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
WARNING: Maven 2.1 and GPG plugin interaction problems.....
This is just a warning that the Maven team has just discovered an interaction problem between Maven 2.1 and the maven-gpg-plugin that CAN result in the signatures for the installed/deployed poms being invalid. Signatures for the other artifacts (jars, wars, etc..) are unaffected and not all poms are affected. Thus, at this point, it's advisable to either use Maven 2.0.10 for releases or verify, check, and resign any affected poms. The Maven team is aware of the situation and is working on a fix. At this point, it's too early to determine if this will require changes to Maven 2.1.x or to the gpg plugin to fix this. However, we felt it was important to get the information out to the users as quickly as possible. -- Daniel Kulp dk...@apache.org http://www.dankulp.com/blog signature.asc Description: This is a digitally signed message part.
dependencySets not filtering during unpacking
Hello, has anyone else run into this problem where a dependencySet isn't filtering during unpacking of a dependency? dependencySet useStrictFilteringtrue/useStrictFiltering outputDirectorysomedir/outputDirectory unpacktrue/unpack unpackOptions includes include**/foo.xml/include /includes filteredtrue/filtered /unpackOptions includes includepackage:artifact:extension:classifier/include /includes /dependencySet The filtered option in unpackOptions doesn't seem to be working - any suggestions?
