On 08.03.19 07:42, Debraj Manna wrote:
Hi
I can see an issue filed for "Maven 3 fails to follow 301 redirects"
https://issues.apache.org/jira/browse/MNG-4816.
Can someone let me know in which version of maven 3.x this is fixed as I am
observing the issue with Maven 3.5 also?
Can yo
could you be referencing
> an old plugin/wagon despite using Maven 3.5?
>
>
> > On Mar 11, 2019, at 12:23 PM, Debraj Manna
> wrote:
> >
> > Anyone any thoughts on this?
> >
> >
> > On Fri, Mar 8, 2019 at 12:12 PM Debraj Manna
> > wrote:
> >
> &
thoughts on this?
>
>
> On Fri, Mar 8, 2019 at 12:12 PM Debraj Manna
> wrote:
>
>> Hi
>>
>> I can see an issue filed for "Maven 3 fails to follow 301 redirects"
>> https://issues.apache.org/jira/browse/MNG-4816.
>>
>> Can someone let me know in w
Anyone any thoughts on this?
On Fri, Mar 8, 2019 at 12:12 PM Debraj Manna
wrote:
> Hi
>
> I can see an issue filed for "Maven 3 fails to follow 301 redirects"
> https://issues.apache.org/jira/browse/MNG-4816.
>
> Can someone let me know in which version of maven
Hi
I can see an issue filed for "Maven 3 fails to follow 301 redirects"
https://issues.apache.org/jira/browse/MNG-4816.
Can someone let me know in which version of maven 3.x this is fixed as I am
observing the issue with Maven 3.5 also?
Thanks,
I would guess that Ivy can work a lot better with Maven repositories than
Maven can with Ivy repositories. I would investigate a one-shot scripted
migration of your Ivy repo to a new Maven repo and force existing publishers
to the Ivy repo to configure Ivy to publish to the new Maven repo.
But I
; Maven 2 and Maven 3 both use the same structure for repositories ( which
> is called a maven2 repo. Yes the name is a bit confusing ).
> If you want Maven to work with a different kind of repository, e.g. ivy to
> maven2, you need to use a repository manager.
> The only one I am aware
Maven 2 and Maven 3 both use the same structure for repositories ( which
is called a maven2 repo. Yes the name is a bit confusing ).
If you want Maven to work with a different kind of repository, e.g. ivy to
maven2, you need to use a repository manager.
The only one I am aware
I was wondering if anyone had any suggestions for working with a
non-standard repository layout?
Basically, I have a Maven 3 project but I need to fetch a fetch artifacts
from an Ivy repository.
http://ant.apache.org/ivy/history/2.0.0/use/info.html
Can Maven handle this directly
-dependency-plugin/src/main/java/org/apache/maven/plugins/dependency/tree/TreeMojo.java#L233
* https://issues.apache.org/jira/browse/MDEP-374
* https://issues.apache.org/jira/browse/MDEP-339
* ...
It used to use Maven2 specific dependency resolution which was now
inconsistent with Maven 3.
Does anybody
gt;> one fixed SNAPSHOT.
>>
>
> Sounds like you don't use a repository manager ?
>
>
>> I upgraded recently to maven 3.
>>
>
> Which version of Maven 3 ? 3.0.5, 3.1.1, 3.2.5, 3.3.3 ?
>
>
> With maven 3, we see that the timestamps are different for each mod
when we wanted to use
one fixed SNAPSHOT.
Sounds like you don't use a repository manager ?
I upgraded recently to maven 3.
Which version of Maven 3 ? 3.0.5, 3.1.1, 3.2.5, 3.3.3 ?
With maven 3, we see that the timestamps are different for each module and
it is now more complicated to use
Dear all,
I was using maven 2 and the unique version for SNAPSHOT deployment.
In this configuration if I deploy a multi-module project, I had a single
timestamp for all the modules which was very useful when we wanted to use
one fixed SNAPSHOT.
I upgraded recently to maven 3.
With maven 3, we see
for Maven 3 only?
Thanks
-Dan
Currently is very cumbersome to inject
@Component(hint = mng-4384)
protected SecDispatcher securityDispatcher;
and Component.xml under resource
This works for both maven 2 and 3
Is there a better way for Maven 3 only?
Thanks
-Dan
I guess you mean you don't have any plugin tag in your pom.xml.
Under build/plugins declare a plugin block like this to override the
inherited version
plugin
artifactIdmaven-checkstyle-plugin/artifactId
version6.3/version
/plugin
Btw, you should be aware that always pinning the plugin
The configuration you did binds an execution to the validate phase. Calling
checkstyle:checkstyle won't pick up this configuration.
The error you get when calling mvn validate (or any later phase) is
because RedundantThrowsCheck
has been removed in Checkstyle 6.2 (according to Checkstyle release
Hello,
I'm using Maven 3.2.5 and I would like to use the Checkstyle plugin in the
newest version (6.3).
The default installation is 5.8, so how can I add the 6.3 version of the plugin
at my pom.xml and
use it on the check goal at the validate phase?
I don’t found the correct pom entries to do
Hi,
apply
http://maven.apache.org/plugins/maven-checkstyle-plugin/usage.html#Checking_for_Violations_as_Part_of_the_Build
and
http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/upgrading-checkstyle.html
Vincent
2015-02-13 21:28 GMT+01:00 Philipp Kraus philipp.kr...@flashpixx.de:
Thanks I have read these instructions, but check style uses the sun_checks.xml
I have add to my build section:
pluginManagement
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-checkstyle-plugin/artifactId
version2.14/version
Hello,
I'm using Maven 3.2.5 and I would like to use the Checkstyle plugin in the
newest version (6.3).
The default installation is 5.8, so how can I add the 6.3 version of the plugin
at my pom.xml and
use it on the check goal at the validate phase?
Thanks a lot
Phil
Hi!
The plugins you are mentioning are still based on Maven 2. Neither have I found
any plugin using aether and the Maven 3 api, nor seems any deeper documentation
to be available. Maven 3 has been released years ago. I thought it would be
worth trying its new API rather than sticking
Best not to directly deal with aether, but to use abstraction
like DependencyGraphBuilder which uses aether when under maven 3
-D
On Tue, Aug 5, 2014 at 5:21 AM, Johannes Schneider jsd...@gmx.de wrote:
Hi!
The plugins you are mentioning are still based on Maven 2. Neither have I
found any
Hi,
I am developing a plugin that needs to query the repositories. I'm using the
Aether API because I thought that's the Maven 3 way to do it (cf.
http://blog.sonatype.com/2011/01/how-to-use-aether-in-maven-plugins/) and
because many of the Maven 2 methods are marked as deprecated. With Maven
On Mon, Jul 28, 2014 at 1:12 AM, Johannes Schneider jsd...@gmx.de wrote:
Hi,
I am developing a plugin that needs to query the repositories. I'm using
the Aether API because I thought that's the Maven 3 way to do it (cf.
http://blog.sonatype.com/2011/01/how-to-use-aether-in-maven-plugins
ArtifactResolver has been deprecated but it doesn't provide guidance on an
appropriate replacement.
http://maven.apache.org/ref/3.2.1/maven-compat/apidocs/index.html
In the spirit of trying to move in the right direction what should I use
instead?
William
On May 25, 2014, at 4:20 AM, William Ferguson william.fergu...@xandar.com.au
wrote:
ArtifactResolver has been deprecated but it doesn't provide guidance on an
appropriate replacement.
http://maven.apache.org/ref/3.2.1/maven-compat/apidocs/index.html
In the spirit of trying to move in the
Subject: Re: Replacement for ArtifactResolver in Maven-3?
From: dk...@apache.org
Date: Sun, 25 May 2014 08:18:31 -0400
To: users@maven.apache.org
On May 25, 2014, at 4:20 AM, William Ferguson
william.fergu...@xandar.com.au wrote:
ArtifactResolver has been deprecated
Thanks. Much appreciated.
On Mon, May 26, 2014 at 5:08 AM, Martin Gainty mgai...@hotmail.com wrote:
Subject: Re: Replacement for ArtifactResolver in Maven-3?
From: dk...@apache.org
Date: Sun, 25 May 2014 08:18:31 -0400
To: users@maven.apache.org
On May 25, 2014, at 4:20 AM
Hi
For Maven 3 compatibility you need to use maven-checkstyle-plugin 2.5 or
newer.
On Thu, Jun 20, 2013 at 1:25 AM, Adam Crume adamcr...@gmail.com wrote:
Checkstyle crashes when I run it with Maven 3.0.4, but works with Maven
2.2.1.
I'm afraid I don't know enough about Maven to create
in
DefaultCheckstyleRssGenerator.generateRSS in Maven 3
From: adamcr...@gmail.com
To: users@maven.apache.org
Checkstyle crashes when I run it with Maven 3.0.4, but works with Maven
2.2.1.
I'm afraid I don't know enough about Maven to create a smaller test case
than this:
1. Set JAVA_HOME to a 1.6 JDK
2. Clone http
Checkstyle crashes when I run it with Maven 3.0.4, but works with Maven
2.2.1.
I'm afraid I don't know enough about Maven to create a smaller test case
than this:
1. Set JAVA_HOME to a 1.6 JDK
2. Clone http://github.com/nasa/mct
3. Follow the steps in README.md, using Maven 3
[ERROR] Failed
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-checkstyle-plugin:2.4:checkstyle
(published-api-checks) on project mct-platform: Execution
published-api-checks of goal
org.apache.maven.plugins:maven-checkstyle-plugin:2.4:checkstyle failed.
NullPointerException - [Help 1]
Check
in general).
Stephen Connolly wrote:
IIRC another issue was that if the parent from the
reactor has a different version from the parent specified
in the pom, Maven 2.x just uses the one from the reactor
while with this fix Maven 3.x will correctly attempt to
download and use
(3) is not following any accepted pattern that
Maven supports.
It seems this was an accepted pattern in Maven 2 but not in
Maven 3. Or are you saying this was not an accepted pattern in
Maven 2 either, and worked by fluke?
As you suggested previously I will bring this subject to the
dev list
-issue.
I believe this is how Maven 2 works.
Your case (3) is not following any accepted pattern that
Maven supports.
It seems this was an accepted pattern in Maven 2 but not in
Maven 3. Or are you saying this was not an accepted pattern in
Maven 2 either, and worked by fluke?
Didn't dig
the reactor, and resolve parent+dependencies in
the next phase. Then this is a non-issue.
I believe this is how Maven 2 works.
Your case (3) is not following any accepted pattern that
Maven supports.
It seems this was an accepted pattern in Maven 2 but not in
Maven 3. Or are you saying
.
In Maven 2 there is success when building the feature workspace
from root, but Maven 3 fails.
To get it working in Maven 3 we either have to maintain
relativePath elements that are different for every feature-branch
(and deal with them when merging back into main = error-prone
to refer to the local checkout of parent.
As you can see, module1 can not make any assumption about
what filesystem directory the parent module resides in, so no
relativePath element can be added.
In Maven 2 there is success when building the feature workspace
from root, but Maven 3 fails
to the local checkout of parent.
As you can see, module1 can not make any assumption about
what filesystem directory the parent module resides in, so no
relativePath element can be added.
In Maven 2 there is success when building the feature workspace
from root, but Maven 3 fails.
To get it working
[Note: this entire post deals with project layouts where it is
undesired for modules to know in what filesystem directory their
parent module resides. This rules out relying on Maven parent
found in parent directory or through the relativePath element.]
Maven 3 will throw a Non-resolvable
. This rules out relying on Maven parent
found in parent directory or through the relativePath element.]
Maven 3 will throw a Non-resolvable parent POM error the first
time this project layout is built, even when built from the
aggregation root:
app/
pom.xml (modules=parent,submodule
I'm trying to make the point that Maven 2 had the expected
behaviour, and Maven 3 changed that into something less
good. As far as I can read the motivation, it seems to have
been done for the wrong reason.
But it's quite likely I'm missing something, and that a
better motivation may be found
?
Regards,
Russ
On May 23, 2013, at 5:05 PM, Mike Wilson mike...@hotmail.com wrote:
I'm trying to make the point that Maven 2 had the expected
behaviour, and Maven 3 changed that into something less
good. As far as I can read the motivation, it seems to have
been done for the wrong reason
Hi Martin,
Sorry for the late response- what is the forking you are doing there?
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-3-does-not-manage-to-deploy-nar-artifact-on-Linux-tp5730943p5747602.html
Sent from the Maven - Users mailing list archive at Nabble.com
I moved this ticket to the dependency plugin.
/Anders
On Tue, Feb 12, 2013 at 6:55 AM, Richard Vowles
rich...@bluetrainsoftware.com wrote:
I made a bug report focused on the disappearing dependencies in Aether.
http://jira.codehaus.org/browse/MNG-5433
Even if I find this bug critical I think nobody had the time to study
it more deeply (me the first) and for now I'm always downgrading to
maven 2 and the dependency plugin 2.4 when I have to use either the
tree or the list goals (which is a mess).
Like you I provided some logs but I didn't
Ok - so is anyone actively working on it? I suspect finding what the bug is
will make it easier to create a test case for it, so if no-one else has the
time, I will find the time.
Thanks!
Richard
On Wed, Feb 13, 2013 at 12:22 AM, Arnaud Héritier aherit...@gmail.comwrote:
Even if I find this
Maven 3 seems to have problems with its dependency resolution. On the same
project a dependency:list returns results that are different (in terms of
scope and actual artifacts) that are different between the two requests.
The Maven 2 one is right - there is no way that our AspectJ stuff isn't
I made a bug report focused on the disappearing dependencies in Aether.
http://jira.codehaus.org/browse/MNG-5433
Yes there are some known issues already open in the dependency plugin
Jira. The bug is somewhere in the dependency walker of aether. It
seems that aether has the right deps but it doesn't allow plugins (I
had the bug in dependency plugin but also in enforcer) to browse these
deps accordingly to
So do we know if they are being worked on?
Is there a page somewhere that might explain where to start to find aether
bugs? I remember the last time I looked and it was seriously confusing :-)
Thanks for the heads up.
On Feb 12, 2013 7:26 PM, Arnaud Héritier aherit...@gmail.com wrote:
Yes
That is really a default value not an expression
On 17 January 2013 17:01, Huang, Roger roghu...@paypal.com wrote:
Is there a way to specify an expression for the Mojo annotation @parameter
in Maven 3?
I have a Mojo, GenerateConfigMojo.java, with property
deliverableSettings of type
Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Sent: Thursday, January 17, 2013 11:04 AM
To: Maven Users List
Subject: Re: How to specify an expression for a Mojo annotation parameter in
Maven 3?
That is really a default value not an expression
On 17 January 2013 17:01
): No connector available to access
repository local.repository (file:../../local.repository/trunk) of type
legacy using the available factories WagonRepositoryConnectorFactory
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-3-warnings-Failure-to-transfer-asm-asm-maven-metadata-xml
did you try adding the wagon-file as an extension ? (it's not anymore
included with maven 3.x)
extensions
extension
groupIdorg.apache.maven.wagon/groupId
artifactIdwagon-file/artifactId
version2.1/version
/extension
/extensions
2013/1/10 pradeep
goals
goalcheck/goal
/goals
/execution
/executions
/plugin
/plugins
/build
any thing that i am missing..??
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-3-warnings-Failure-to-transfer-asm-asm-maven-metadata-xml
this message in context: http://maven.40175.n5.nabble.com/Maven-3-does-
not-manage-to-deploy-nar-artifact-on-Linux-tp5730943p5730959.html
Sent from the Maven - Users mailing list archive at Nabble.com.
may i know what is that definition that i need to include for nar plugin ?
and where
:
Hi,
While trying to migrate a project from Maven 2 to Maven 3, I
encountered a problem, the essence of which can be demonstrated by the
following simple example.
Consider the following POM:
project
modelVersion4.0.0/modelVersion
groupIdtest/groupId
artifactIdA/artifactId
Hi,
While trying to migrate a project from Maven 2 to Maven 3, I
encountered a problem, the essence of which can be demonstrated by the
following simple example.
Consider the following POM:
project
modelVersion4.0.0/modelVersion
groupIdtest/groupId
artifactIdA/artifactId
Hello all,
I have a build failed with the following error when I try to build my webapp
:
[ERROR] Failed to execute goal on project my-webapp: Could not resolve
dependencies for project com.edeal.frontline: my -webapp:war:Head-SNAPSHOT:
Could not find artifact org.json.rpc:jsonrpc:jar:1.0 -
as expected.
However- when I try to use maven 3, in the deploy phase I receive:
[INFO] Scanning for projects...
[ERROR] The build could not read 1 project - [Help 1]
[ERROR]
[ERROR] The project com.hp.bsm.sha.native:paris:1.00-SNAPSHOT
(/NAS_ROOT/users/bsmbuild/EC_Builds/bsm-sha/sha-native/trunk
One line was not written well-
[ERROR] Unknown packaging: nar @ line 14, column 14
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-3-does-not-manage-to-deploy-nar-artifact-on-Linux-tp5730943p5730944.html
Sent from the Maven - Users mailing list archive
Which version of maven-nar-plugin are you using?
On Wed, Nov 14, 2012 at 12:19 PM, Eyal Goren eyalg1...@gmail.com wrote:
One line was not written well-
[ERROR] Unknown packaging: nar @ line 14, column 14
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-3
Also- I am using maven 3.0.3
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-3-does-not-manage-to-deploy-nar-artifact-on-Linux-tp5730943p5730946.html
Sent from the Maven - Users mailing list archive at Nabble.com
14, 2012 at 12:27 PM, Eyal Goren eyalg1...@gmail.com wrote:
Also- I am using maven 3.0.3
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-3-does-not-manage-to-deploy-nar-artifact-on-Linux-tp5730943p5730946.html
Sent from the Maven - Users mailing list archive
and deploy it)
Eyal
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-3-does-not-manage-to-deploy-nar-artifact-on-Linux-tp5730943p5730949.html
Sent from the Maven - Users mailing list archive at Nabble.com
Any how- I took the sources from that location after Oct 2010, so it is the
same pom (I just change the ant cpp tasks version since I needed to add
changes there too)
Eyal
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-3-does-not-manage-to-deploy-nar-artifact-on-Linux
: Re: Maven 3 does not manage to deploy nar artifact on Linux
Any how- I took the sources from that location after Oct 2010, so it is the
same pom (I just change the ant cpp tasks version since I needed to add
changes there too)
Eyal
--
View this message in context:
http://maven
.nabble.com/Maven-3-does-not-manage-to-deploy-nar-artifact-on-Linux-tp5730943p5730959.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands
of the nar plugin were in the profile.
I used the most updated code (I think it was 2.0-SNAPSHOT). any how- I took
the most updated code.
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-3-does-not-manage-to-deploy-nar-artifact-on-Linux-tp5730943p5730959.html
Sent
How can I cure best the problems shown below? it occurs during a
bootstrap-build of maven-3/trunk on my Vista System.
(see red lines, which are of interesst to me).
I have successfully build from sources SLF4J é all. Where does this
bootstrap-build.xml expect this files now?
where do I have
On Thu, Nov 1, 2012 at 6:29 AM, Stadelmann Josef
josef.stadelm...@axa-winterthur.ch wrote:
How can I cure best the problems shown below? it occurs during a
bootstrap-build of maven-3/trunk on my Vista System.
(see red lines, which are of interesst to me).
We can't. This mailing list strips
: Benson Margulies [mailto:bimargul...@gmail.com]
Gesendet: Donnerstag, 1. November 2012 11:39
An: Maven Users List
Betreff: Re: [maven-3/trunk] bootstrap-build failing
On Thu, Nov 1, 2012 at 6:29 AM, Stadelmann Josef
josef.stadelm...@axa-winterthur.ch wrote:
How can I cure best the problems shown
On 01 Nov 2012, at 12:43 PM, Stadelmann Josef
josef.stadelm...@axa-winterthur.ch wrote:
What does that mean?
are you saying that maven developers will not fix the bootstrap-build problem
shown below or
are you saying that This mailing list strips HTML I have delivered
insufficient
While you're at it: Give us info on what version of Ant you're using as
well what JDK version. If you want to speed things up, you could try a
different Ant version. (I don't know which Ant version is preferred though
as I always build with Maven.)
The slf4j error is most likely safe to ignore.
Thanks Graham
OK, that's my fault, thanks to indicate it. So here is my original e-mails
again hopefully this time as text only.
How can I cure best the problems shown below? it occurs during a
bootstrap-build of maven-3/trunk on my Vista System.
the ANT version is 1.8.2
please see lines
, 1. November 2012 12:11
An: Maven Users List
Betreff: Re: [maven-3/trunk] bootstrap-build failing
While you're at it: Give us info on what version of Ant you're using as well
what JDK version. If you want to speed things up, you could try a different Ant
version. (I don't know which Ant version
. November 2012 11:39
An: Maven Users List
Betreff: Re: [maven-3/trunk] bootstrap-build failing
On Thu, Nov 1, 2012 at 6:29 AM, Stadelmann Josef
josef.stadelm...@axa-winterthur.ch wrote:
How can I cure best the problems shown below? it occurs during a
bootstrap-build of maven-3/trunk on my Vista
On 1 November 2012 10:29, Stadelmann Josef
josef.stadelm...@axa-winterthur.ch wrote:
How can I cure best the problems shown below? it occurs during a
bootstrap-build of maven-3/trunk on my Vista System.
(see red lines, which are of interesst to me).
I have successfully build from sources
OK Stuart,
at my Vista System, it fails. Just downloaded and installed ant 1.8.4
$ java -version
java version 1.6.0_30
Java(TM) SE Runtime Environment (build 1.6.0_30-b12)
Java HotSpot(TM) Client VM (build 20.5-b03, mixed mode)
C770817@C036357 /e/asf/maven/maven-3/trunk
$ ant -version
Apache
@C036357 /e/asf/maven/maven-3/trunk
$ ant -version
Apache Ant(TM) version 1.8.4 compiled on May 22 2012
$ ant -d -f build.xml
...
BUILD FAILED
E:\asf\maven\maven-3\trunk\build.xml:250: Java returned: 1
at org.apache.tools.ant.taskdefs.Java.execute(Java.java:111
java version 1.6.0_30
Java(TM) SE Runtime Environment (build 1.6.0_30-b12)
Java HotSpot(TM) Client VM (build 20.5-b03, mixed mode)
C770817@C036357 /e/asf/maven/maven-3/trunk
$ ant -version
Apache Ant(TM) version 1.8.4 compiled on May 22 2012
$ ant -d -f build.xml
...
BUILD
: Donnerstag, 1. November 2012 17:23
An: Maven Users List
Betreff: Re: AW: [maven-3/trunk] bootstrap-build failing
I'm guessing there's a missing proxy configuration here.
/Anders
On Thu, Nov 1, 2012 at 4:42 PM, Stuart McCulloch mccu...@gmail.com wrote:
On 1 Nov 2012, at 15:06, Stadelmann Josef wrote
Hello
Back in Maven 2, when executing a plugin goal from command line,
Maven always tries to look for latest version and its snapshot
In Maven 3, this capability disappear, Maven only looks for latest
released version.
Would it possible to turn it on from command line?
I fully understand
dant...@gmail.com wrote:
Hello
Back in Maven 2, when executing a plugin goal from command line,
Maven always tries to look for latest version and its snapshot
In Maven 3, this capability disappear, Maven only looks for latest
released version.
Would it possible to turn it on from command line
-SNAPSHOT:goal
That's it.
On 9/27/12 10:35 AM, Dan Tran dant...@gmail.com wrote:
Hello
Back in Maven 2, when executing a plugin goal from command line,
Maven always tries to look for latest version and its snapshot
In Maven 3, this capability disappear, Maven only looks for latest
version and its snapshot
In Maven 3, this capability disappear, Maven only looks for latest
released version.
Would it possible to turn it on from command line?
I fully understand the benefit of predictability. However, it becomes
very inconvenient to cut the plugin release while still testing
Dan Tran wrote:
hi Jörg
The problem here is I run my plugin from command line, no pom.
Then all you can do is to follow Roy's example.
- Jörg
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional
I was hoping like 'mvn -another-flag myplugin:goal'
I am surely understand the long name, for those ppl dont know too much
about maven will resist to use. but that is another story
Thank you
-D
On Thu, Sep 27, 2012 at 3:31 PM, Jörg Schaible joerg.schai...@gmx.de wrote:
Dan Tran wrote:
hi
Hi all,
In Maven 3.0.4 and am seeing the following error when I try to release a
project.
[INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @
rpm-maven-plugin ---
Uploading:
Am 23.08.2012 12:38, schrieb Nord, James:
Hi all,
In Maven 3.0.4 and am seeing the following error when I try to release a
project.
[INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @
rpm-maven-plugin ---
Uploading:
On Thu, Aug 23, 2012 at 4:30 PM, Thomas Scheffler
thomas.scheff...@uni-jena.de wrote:
Am 23.08.2012 12:38, schrieb Nord, James:
Hi all,
In Maven 3.0.4 and am seeing the following error when I try to release a
project.
[INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @
-Original Message-
From: Thomas Broyer [mailto:t.bro...@gmail.com]
Sent: 23 August 2012 15:44
To: Maven Users List
Subject: Re: Maven 3 deployment authentication
On Thu, Aug 23, 2012 at 4:30 PM, Thomas Scheffler thomas.scheffler@uni-
jena.de wrote:
Am 23.08.2012 12:38, schrieb
,
sorry to bump ... :-(
but I'm still having issues understanding what's wrong with the maven
dependency plugin and maven 3...
I attached a pom to demonstrate the problem :
Using maven 3,
1) do a mvn package
2) then do a mvn
org.apache.maven.plugins:maven-dependency-plugin:2.4:purge
and maven 3
From what I recall, nobody has yet updated dependency:tree to query
aether's graph directly rather than go through the emulation of 2.x's API
for examining the dependency tree. When I last chatted on this with
Benjamin, he left me with the distinct impression that I should not rely
send and receive email on the
basis of the terms set out at www.ericsson.com/email_disclaimer
-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Sent: Monday, June 04, 2012 4:10 PM
To: Maven Users List
Subject: Re: maven dependency plugin and maven 3
at www.ericsson.com/email_disclaimer
-Original Message-
From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On Behalf Of
Anders Hammar
Sent: Monday, June 04, 2012 5:24 PM
To: Maven Users List
Subject: Re: maven dependency plugin and maven 3
Please don't hijack someone
for javax.servlet:servlet-api:jar:2.5
[WARNING] Missing POM for net.dahanne.gallery:commons-gallery:jar:2.1.0-SNAPSHOT
even though those 2 artifacts are existing in my local repo.
So I created a bug in the maven dependency plugin Jira :
http://jira.codehaus.org/browse/MDEP-356
to consider the use of maven 3
[WARNING] Missing POM for javax.servlet:servlet-api:jar:2.5
[WARNING] Missing POM for
net.dahanne.gallery:commons-gallery:jar:2.1.0-SNAPSHOT
even though those 2 artifacts are existing in my local repo.
Have you looked at the content of those pom files to ensure they
aren't corrupted?
Wayne
1 - 100 of 601 matches
Mail list logo
