Would it make sense to branch from 2.1 and do a controlled update? What
version of maven core are we willing to require?
On Wed, May 13, 2020 at 1:41 PM Benson Margulies
wrote:
> 2.1 has a terrible bug; it does not compensate for long-ago changes in
> which ArtifactItem.getClassifier() returns
2.1 has a terrible bug; it does not compensate for long-ago changes in
which ArtifactItem.getClassifier() returns null instead of "".
I think then perhaps branching it and making a 2.1.1 is called for.
On Wed, May 13, 2020 at 5:52 AM Karl Heinz Marbaise
wrote:
> Hi,
>
> On 13.05.20 01:59, Bens
maven-plugin-testing-harness 2.1 should work for most cases, and many
of our plugins are not that far up to date yet.
But yes, we do have a major issue with failing to update deep
dependencies like plexus, aether, sisu, maven core, and the testing
harness across all the repos.
On Wed, May 13, 202
Right I saw this problems, maven testing plugin next version 3.3.0 (
released 2014) requires Maven core 3.2.5 - so it will not be useful for
long time ..
Sylwester
śr., 13 maj 2020, 14:52 użytkownik Karl Heinz Marbaise
napisał:
> Hi,
>
> On 13.05.20 01:59, Benson Margulies wrote:
> > What's cur
Hi,
On 13.05.20 01:59, Benson Margulies wrote:
What's current best practice for updating the versions of the test harness
and other bits and bobs?
the problem with Test harness is that it brings more recent versions of
maven-core with it which is from my point of view a no go for test
harness
It's a very good thing to do. That said, updating the test harness is
usually a lot more difficult than it looks. It tends to pull in
incompatible versions of Plexus, Sisu, and Aether requiring a lot of
code changes throughout the plugin.
On Tue, May 12, 2020 at 8:00 PM Benson Margulies wrote:
>
There has been a (short) discussion on this topic recently in this list
[1].
Although it contained no formal vote, my provisional conclusion would be
to create a JIRA ticket and then provide a merge request.
Thanks,
Maarten
[1]
https://lists.apache.org/thread.html/r3b921993565a04ea0c20e6439d
What's current best practice for updating the versions of the test harness
and other bits and bobs?
Hello all,
I am a tad puzzled here. I got a strange exception from the
maven-checkstyle-plugin during its site generation yesterday. The immediate
reason in the code was rather simple to track and fix (it is done in PR
https://github.com/apache/maven-plugins/pull/88). I also created a
discussion a
I want to start Maven directly in Java and add more dependencies to a
plugin witout modifying POM file.
This means the Maven should run as Java object.
Is this hack possible?
Cheers
Tibor
After having to disable my maven mirror for one reason or another awhile ago
I now seem to be getting hit with this rather annoying bug on quite a few
projects now that my ~/.m2/repository has a mix of artifacts downloaded via
a mirror, and others direct.
rm'ing the _maven.repositories file from ~
I've pulled all the version ranges out of the artefacts and I still can't
release the plugin. I'm just firing up maven in debug again.
But yeah, being able to have maven users use the latest version of easyb
would really be nice.
Richard
On Tue, May 24, 2011 at 7:07 PM, Mark Derricutt wrote:
>
Has there been any movement on this at all?Beyond the few messages here
and only Richards comments on the JIRA ticket it doesn't look like anyways
had a chance to look further into this.
>From memory there's less than a handful of folk who know how the dependency
resolution works, more so now
On Sat, May 14, 2011 at 6:43 AM, Richard Vowles
wrote:
> On Sat, May 14, 2011 at 12:08 AM, Barrie Treloar wrote:
>
>>
>
> I can hack your pom to get it to work by forcing the dependency via:
>>
>>
>>
>> org.codehaus.groovy
>> groovy-all
>> 1.7.10
>>
>>
>
On Sat, May 14, 2011 at 12:08 AM, Barrie Treloar wrote:
>
I can hack your pom to get it to work by forcing the dependency via:
>
>
>
>org.codehaus.groovy
>groovy-all
>1.7.10
>
>
>
>
I have no problem with a hacked pom to workaround it.
>
> Maybe
I can't see where your problem is, I never do version ranges.
I can hack your pom to get it to work by forcing the dependency via:
org.codehaus.groovy
groovy-all
1.7.10
Maybe someone else can tell us why in the easyb jar a version of
'lo all,
I was just pointed at http://jira.codehaus.org/browse/MNG-2742 by a friend
and was wondering if anyone knew what the state of it was?
The problem is around version ranges not working for plugin dependencies.
Looking at the comments in the original ticket I see Mathew Adams was
On 01/12/2008, at 4:58 AM, jallen wrote:
Should this be detected by mvn and prevented?
Yes (I'm surprised it isn't, I thought plugin dependencies were in the
reactor ordering).
So bottom line question, what is the specified behaviour for what
I'm doing?
Does maven try
faults for scm, distrMgt and a bunch of other stuff. I suppose I
could make the config artifact completely stand-alone, duplicating the corp
pom static stuff in its pom so its no longer involved in the reactor.
Thoughts, comments and admonishments welcome,
John
--
View this message in context:
I think ${plugin.artifacts} works.
- Brett
On 24/06/2008, at 8:16 PM, nicolas de loof wrote:
Hello,
from a plugin (the mojo sandbox gwt-maven-plugin) I need to access
one of
the plugin dependencies as a File.
How can I retrieve the plugin MavenProject, or any equivalent, to
retrieve
Hello,
from a plugin (the mojo sandbox gwt-maven-plugin) I need to access one of
the plugin dependencies as a File.
How can I retrieve the plugin MavenProject, or any equivalent, to retrieve
the dependency as an Artifact or File ?
I have the ugly option to cast the classloader to URLClassLoader
Ugh!! :-(
Thanks for the help Arnaud, Xavier, and Lukas...
> -Original Message-
> From: Arnaud HERITIER [mailto:[EMAIL PROTECTED]
> Sent: Saturday, December 01, 2007 4:33 PM
> To: Maven Developers List
> Subject: Re: [m1] PMD plugin dependencies
>
> Hi Xavier,
&g
Hi Xavier,
Thanks a lot for your feedback !
Jeff, you know what to do if you want to use the new version of pmd in
maven 1 land.
Arnaud
On Nov 30, 2007 7:49 PM, Xavier Le Vourch <[EMAIL PROTECTED]>
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi,
>
>
> Arnaud HERITIER wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Arnaud HERITIER wrote:
> I hope that 1.1.1 is compatible with 1.1-beta-9. Depending of the part of
> jaxen which is used by pmd it's possible that it works fine with the old
> version.
First, let me give you some general info: I'm an admin fo
TED]
> Sent: Friday, November 30, 2007 1:34 AM
> To: Maven Developers List
> Subject: Re: [m1] PMD plugin dependencies
>
> yes if you want. we can produce minor updates by upgrading some
dependencies
> if it helps to improve plugins.
>
> Arnaud
>
> On Nov 30, 2007
TED]
> Sent: Friday, November 30, 2007 1:34 AM
> To: Maven Developers List
> Subject: Re: [m1] PMD plugin dependencies
>
> yes if you want. we can produce minor updates by upgrading some
dependencies
> if it helps to improve plugins.
>
> Arnaud
>
> On Nov 30, 2007
yes if you want. we can produce minor updates by upgrading some dependencies
if it helps to improve plugins.
Arnaud
On Nov 30, 2007 7:52 AM, Lukas Theussl <[EMAIL PROTECTED]> wrote:
> Bad news: jaxen is used in the core [1]
> Good news: Arnaud had already upgraded a lot of deps and attached
> pa
Bad news: jaxen is used in the core [1]
Good news: Arnaud had already upgraded a lot of deps and attached
patches (MAVEN-1797 - 1805), among them for jaxen [2]
Should we work on m1.1.1 with only upgraded deps?
:)
-Lukas
[1] http://maven.apache.org/maven-1.x/dependencies.html
[2] http://jira.c
Hi jeff,
What you have to check, it is if jaxen is loaded by the core. If that's
the case, the version in the core is always used.
If not, it is the version of jaxen used by the first plugin loaded which
use it.
That's why we tried for the 1.1 release of maven to align dependencies to
have l
Hi Arnaud,
PMD 4.1 has updated its deps (e.g. asm and jaxen), and I am concerned on
upgrading the plugin. I know you (and possibly others) spent considerable
time aligning the dependencies amongst core and many other plugins. I know
Jaxen was one of them.
Do you have concerns/suggestions on upda
Hi,
I've got some plugins, which currently do have static dependencies:
The maven-jaxme-plugin, the Axis 2 plugins, the rat-maven-plugin, and
some inhouse plugins at my employers site. I've always disliked these
static dependencies and recently I have written some code for an
inhouse project that
[ http://jira.codehaus.org/browse/MNG-1836?page=all ]
Carlos Sanchez closed MNG-1836:
---
Resolution: Duplicate
It duplicates that and the related issues, they are caused by the same problem
> inherited plugin dependenc
h the build in the child project, the dependencies are
correctly loaded.
> inherited plugin dependencies
> -
>
> Key: MNG-1836
> URL: http://jira.codehaus.org/browse/MNG-1836
> Project: Maven 2
> Type: Bug
>
[ http://jira.codehaus.org/browse/MNG-1836?page=all ]
Carlos Sanchez closed MNG-1836:
---
Assign To: Carlos Sanchez
Resolution: Duplicate
> inherited plugin dependencies
> -
>
> Key: MNG-1836
&g
project-level plugin dependencies not handled correctly in multimodule builds
-
Key: MNG-1949
URL: http://jira.codehaus.org/browse/MNG-1949
Project: Maven 2
Type: Bug
Components: Plugins
[ http://jira.codehaus.org/browse/MNG-1896?page=all ]
Brett Porter closed MNG-1896:
-
Assign To: Brett Porter
Resolution: Duplicate
> Can't load a class from a plugin, when this class is in a parent
> pom's/build/pluginManagemen
Can't load a class from a plugin, when this class is in a parent
pom's/build/pluginManagement/plugins/plugin/dependencies
-
Key: MNG-1896
inherited plugin dependencies
-
Key: MNG-1836
URL: http://jira.codehaus.org/browse/MNG-1836
Project: Maven 2
Type: Bug
Versions: 2.0
Reporter: Gilles Scokart
I have project composed of a reactor/parent pom.xml and a few
[ http://jira.codehaus.org/browse/MNG-1804?page=all ]
Brett Porter closed MNG-1804:
-
Resolution: Fixed
Fix Version: 2.0.1
> Can't load a class from a plugin, when this class is in a user's
> pom/build/plugins/plu
ThreadContextCL work. Cool.
> Can't load a class from a plugin, when this class is in a user's
> pom/build/plugins/plugin/dependencies
> --
>
> Key: MNG-1804
> U
Can't load a class from a plugin, when this class is in a user's
pom/build/plugins/plugin/dependencies
--
Key: MNG-1804
URL: http://jira.codehaus.org/browse/MNG-1804
[ http://jira.codehaus.org/browse/MAVEN-1478?page=all ]
Brett Porter updated MAVEN-1478:
Assign To: (was: Brett Porter)
> document plugin dependencies
>
>
> Key: MAVEN-1478
>
[ http://jira.codehaus.org/browse/MNG-836?page=comments#action_46280 ]
Kenney Westerhof commented on MNG-836:
--
I fixed this in r278736, 2005-09-05...
> plugin dependencies cannot be resolved
> --
>
>
[ http://jira.codehaus.org/browse/MNG-836?page=comments#action_46260 ]
Brett Porter commented on MNG-836:
--
we're presently back to where we were, but the above can be used to form a test
case
> plugin dependencies cannot be
[ http://jira.codehaus.org/browse/MNG-836?page=comments#action_46235 ]
John Casey commented on MNG-836:
Do we have a test to prevent this regression in future, or are we no better off
than before??
> plugin dependencies cannot be resol
[ http://jira.codehaus.org/browse/MNG-836?page=all ]
Brett Porter closed MNG-836:
Resolution: Fixed
was a regression caused by MNG-757, rolled back
> plugin dependencies cannot be resolved
> --
>
>
[ http://jira.codehaus.org/browse/MNG-836?page=all ]
Kenney Westerhof updated MNG-836:
-
Description:
Try: deleting ~/.m2/repository/org/codehaus and then build maven-model.
Somehow plugin dependencies are not resolved; weird that this doesn&#
plugin dependencies cannot be resolved when repository has same .
-
Key: MNG-836
URL: http://jira.codehaus.org/browse/MNG-836
Project: Maven 2
Type: Bug
Versions: 2.0-beta-1
Reporter
[ http://jira.codehaus.org/browse/MAVEN-1478?page=all ]
Brett Porter updated MAVEN-1478:
Fix Version: (was: 1.1-beta-2)
1.1-rc1
> document plugin dependencies
>
>
> Key
[ http://jira.codehaus.org/browse/MNG-355?page=all ]
Brett Porter closed MNG-355:
Resolution: Duplicate
Fix Version: (was: 2.0-beta-1)
> plugin dependencies are resolved for plugins not necessarily relev
[ http://jira.codehaus.org/browse/MAVEN-1478?page=all ]
Brett Porter updated MAVEN-1478:
Fix Version: (was: 1.1-beta-1)
1.1-beta-2
> document plugin dependencies
>
>
> Key
plugin dependencies are resolved for plugins not necessarily relevant
-
Key: MNG-355
URL: http://jira.codehaus.org/browse/MNG-355
Project: m2
Type: Bug
Components: maven-core
Reporter: Brett
[ http://jira.codehaus.org/browse/MAVEN-1478?page=history ]
Brett Porter updated MAVEN-1478:
Comment: was deleted
> document plugin dependencies
>
>
> Key: MAVEN-1478
> URL: http://jira.code
om
http://www.scotlandbiz.net http://www.thetalkingwalk.co.uk http://www.ukbiz.org
http://www.uk-biz.com http://www.uk-biz.co.uk http://www.veryeasy.biz
http://www.webposters.co.uk http://www.whyshouldi.com
> document plugin dependencies
>
>
> Key: MAVEN-1478
:
-
Key: MAVEN-1478
Summary: document plugin dependencies
Type: Bug
Status: Open
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
documentation
:
-
Key: MAVEN-1478
Summary: document plugin dependencies
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
documentation
Hi all (particularly Carlos who filed the bug :),
I'd appreciate it if anyone using plugin dependencies can test the
latest MAVEN-1_0-BRANCH CVS before 1.0.1 is released to make sure
everything still works as advertised. In particular:
- inside a reactored environment
- in an environment w
:
-
Key: MAVEN-1427
Summary: Plugin dependencies don't delete previous versions
Type: Bug
Status: Closed
Priority: Critical
Resolution: FIXED
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Un
plugin dependencies
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
documentation
Fix Fors:
1.0.1
Assignee:
Reporter: Brett Porter
Created: Sat
: MAVEN-1478
Summary: document plugin dependencies
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
documentation
Fix Fors:
1.0.1
Assignee
:
-
Key: MAVEN-1427
Summary: Plugin dependencies don't delete previous versions
Type: Bug
Status: Unassigned
Priority: Critical
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Fix
:
-
Key: MAVEN-1427
Summary: Plugin dependencies don't delete previous versions
Type: Bug
Status: Unassigned
Priority: Critical
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Fix Fors:
1.1
Versions:
: MAVEN-1427
Summary: Plugin dependencies don't delete previous versions
Type: Bug
Status: Unassigned
Priority: Critical
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Versions:
1.0
Assignee:
Reporter: C
94
Summary: Plugin dependencies don't behave like plugin:download
Type: Bug
Status: Closed
Priority: Critical
Resolution: WON'T FIX
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Assignee:
Reporter: Carlos Sanchez
Cre
Here is an overview of the issue:
-
Key: MAVEN-1394
Summary: Plugin dependencies don't behave like plugin:download
Type: Bug
Status: Unassigned
Priority: Critical
Original Estimate: Unknown
Time
=comments#action_23122
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1394
Here is an overview of the issue:
-
Key: MAVEN-1394
Summary: Plugin
org/browse/MAVEN-1394?page=comments#action_22530
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1394
Here is an overview of the issue:
-
:
-
Key: MAVEN-1394
Summary: Plugin dependencies don't behave like plugin:download
Type: Bug
Status: Unassigned
Priority: Critical
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Ass
: MAVEN-1394
Summary: Plugin dependencies don't behave like plugin:download
Type: Bug
Status: Unassigned
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Assignee:
Reporter: Carlos Sanchez
Created: Fri, 23 Jul 2004 6:
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: mercredi 7 juillet 2004 01:59
> To: Maven Developers List
> Subject: RE: plugin dependencies
>
> Thanks Vincent,
>
> I was more referring to adding a DEPRECATION message inside the
MAIL PROTECTED]
> > Sent: mardi 6 juillet 2004 14:30
> > To: Maven Developers List
> > Subject: plugin dependencies
> >
> > Hi,
> >
> > After dIon prompted me to take a look yesterday afternoon I figured a way
> > to
> > load the plugin co
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: mardi 6 juillet 2004 14:30
> To: Maven Developers List
> Subject: plugin dependencies
>
> Hi,
>
> After dIon prompted me to take a look yesterday afternoon I figured a way
> to
>
Hi,
After dIon prompted me to take a look yesterday afternoon I figured a way to
load the plugin contexts on the fly without messing up the order of things, so
maven:get/maven:set (and their legacy versions pluginVar
and getPluginContext) now initialise a plugin if it is not already initialised.
:
-
Key: MPJAR-22
Summary: Manifest Extension fixes: Ignore plugin dependencies, allow url override.
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Original Estimate: 5 minutes
Time Spent: Unknown
Remaining: 5 minutes
Project: maven-jar-plugin
cure/ViewIssue.jspa?key=MAVEN-1219
Here is an overview of the issue:
-
Key: MAVEN-1219
Summary: Goals from plugin dependencies fail if the plugin is installed as part of
the build process
Type: Bug
St
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1219
Here is an overview of the issue:
-
Key: MAVEN-1219
Summary: Goals from plugin dependencies fail if the plugin is installed as pa
ssue:
-
Key: MAVEN-1219
Summary: Goals from plugin dependencies fail if the plugin is installed as part of
the build process
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unk
ion_18148
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1219
Here is an overview of the issue:
-
Key: MAVEN-1219
Summary: Goals fr
:
-
Key: MAVEN-1219
Summary: Goals from plugin dependencies fail if the plugin is installed as part of
the build process
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
view of the issue:
-
Key: MPJAR-22
Summary: Manifest Extension fixes: Ignore plugin dependencies, allow url override.
Type: Bug
Status: Open
Priority: Major
Original Estimate: 5 minutes
Time Spent: Unk
:
-
Key: MPJAR-22
Summary: Manifest Extension fixes: Ignore plugin dependencies, allow url override.
Type: Bug
Status: Open
Priority: Major
Original Estimate: 5 minutes
Time Spent: Unknown
Remaining: 5 minutes
Project: maven-jar-plugin
Assignee: Jason van
On Wed, 2003-11-26 at 10:31, Vincent Massol wrote:
> > -Original Message-
> > From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> > Sent: 26 November 2003 16:22
> > To: Maven Developers List
> > Subject: Re: Adding explicit plugin dependencies
> >
>
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: 26 November 2003 16:22
> To: Maven Developers List
> Subject: Re: Adding explicit plugin dependencies
>
> On Wed, 2003-11-26 at 03:55, Vincent Massol wrote:
> > Hi,
> >
>
On Wed, 2003-11-26 at 03:55, Vincent Massol wrote:
> Hi,
>
> I'd like to start adding explicit dependencies for maven plugins.
+1
The plugin dependency mechanism will need a little adjusting but that's
not that big of a deal. I'm not sure how much of the dependency
resolving code Brett merged f
Hi,
I'd like to start adding explicit dependencies for maven plugins. Now
that each plugin can be downloaded separately, I think this is a
required step: Let's say I release a new version of plugin X. However,
for this plugin to run I've also modified another plugin Y. When the end
user runs "mave
Worked out that if I add
maven.repo.remote=http://www.ibiblio.org/maven/,http://www.codeczar.com/maven/
to the drivers.properties file within maven.jar.
Is there some other way of changing this value without having to modify
the maven.jar?
cheers
Nathan
Nathan Coast wrote:
Hi,
Is it possible
Hi,
Is it possible for plugins to download their dependencies from another
repository? I tried adding
maven.repo.remote=http://www.ibiblio.org/maven/,http://www.codeczar.com/maven/
to the project.properties for the plugin but the jar files aren't
downloaded? Do I need to specify the addition
87 matches
Mail list logo
