elf hasn't
> upgraded to 1.0. The version used in the core is exported for use in
> plugins.
>
> On Jun 16, 2014, at 6:06 AM, Nigel Magnay wrote:
>
> > Hi
> >
> > I have some pre-existing code that uses org.eclipse.aether, that works
> fine.
> >
> >
Hi
I have some pre-existing code that uses org.eclipse.aether, that works fine.
However, when I reference it and invoke it from a maven-plugin, I get
A required class was missing while executing :
org.eclipse.aether.spi.connector.transport.TransporterFactory
Looking at the urls spat out, it se
On Tue, Mar 25, 2014 at 8:55 AM, Baptiste Mathus wrote:
> FWIW, I'm aware it's easily feasible to add that checksum validation in a
> plugin, but you'll still have to repeat the coordinates.
> And that very thing was my point: I don't think having to repeat those
> coordinates to add metadata is
>
>
> Should the PMC encourage people experimenting on new improvements to Maven
> to do that work at the ASF? And if so, should they then practice what they
> preach, and ensure that any experiments with Maven take place on the ASF
> SCM servers (at least once such experiments become semi-serious
This keeps coming up, over and over and over.
e.g:
http://maven.40175.n5.nabble.com/Meta-information-about-dependencies-in-a-pom-td4971927.html
The maven 'answer' seems to amount to 'hard cheese, you must re-specify
each and every one of your dependencies again in your plugin config'. And
then po
>
>
> I am running Maven inside of Jenkins inside of WebSphere on AIX. I am
> currently hosting Jenkins under WAS 6.1 on AIX 5.3. Whilst AIX 5.3 is
> nearing (or may have reached it's EOS), WAS 6.1's EOS dates have *just been
> extended* by a year!
>
>
You know that Jenkins is looking like going Ja
I am trying to diagnose a failure when running flex-mojos copy-resources
when running a build with clover enabled. I've seen references to this also
being a problem when building with m2e.
Flex-mojos' CopyMojo finds dependencies, then copies them into the output
(for building up a WAR file). To do
>
>
>
> Sorry, but it seems to me that it was simply a wrong approach to define own
> scopes. You run Maven in an undefined state and moan about it's undefined
> behavior.
>
> And the author of the flex plugin has tried, from observation, several
times, to get an answer from the maven-dev community
Well, the problem currently is if you define a pom that declares a number
of dependencies (e.g: the ones you need for the flex framework), and some
of these have custom scopes (e.g: RSL or external), those scopes are
stripped when you include that pom in your project. (IIRC, anything custom
just ge
Yes. It's horrible. It occurs in other places too -- for example, in
environments such as flex, you can declare a dependency with more scopes
than java (merged, internal, external, rsl or caching). If it's an RSL,
then you may choose one of about 4 'application domains' that control how
it will be
Hello
I use flexmojos maven plugin to build flex projects with maven.
Flex projects have more dependency scopes than java projects, which control
various things like caching and runtime dependency loading. To do this,
various scopes are added (e.g: rsl).
This works fine when dependencies are dir
they try to remember which namespace goes with which feature.
>
> On the other hand, if you want to open the door for new information in
> the POM that 'belongs to' particular plugins (e.g. m2e), namespaces
> would at least make logical sense, unless you are persuaded by the
>
>
>
> If tools validate against the schema, they know when a POM is, in
> fact, valid for its declared model. Thus, any elements that the tool
> does not recognize are proved to be 'messengers from the future'.
>
>
It would help enormously if 'messengers from the future' used an appropriate
XML n
There is a fork under the old license here:
https://bitbucket.org/ivertex/java-service-wrapper/overview
On Sun, Jun 12, 2011 at 4:40 PM, Benson Margulies wrote:
> There's no such thing as a 'retroactive license change', though
> perhaps the Tanuki-person has managed a sufficient approximation.
How burnt-in to maven (and repo managers) is the snapshot resolution
metadata ? Specifically, when I pull metadata like
org.company
artifact
2.3-SNAPSHOT
20081030.213329
5
20081030213342
Does the resultant resolved snapshot *have* to be called
artifact-${t
> My vote does not really count here, but Sun aggressively supports
> Mercurial in NetBeans. Based on reviews, Mercurial seemed to initially have
> a technical edge whereas GIT had a loyal following. They do compete
> aggressively and GIT has fixed many of its issues.
>
> NetBeans works better wi
> Do you see that Google choose Mercurial rather than Git ?
>
> Mercurial support for Project Hosting on Google Code
> http://google-code-updates.blogspot.com/2009/04/mercurial-support-for-project-hosting.html
>
> Analysis of Git and Mercurial
> http://code.google.com/p/support/wiki/DVCSAnalysis
>
Umm
m2eclipse is using the 3.x branch, not the 2.1 branch.
On Sun, Feb 8, 2009 at 4:52 PM, Bouiaw wrote:
> From my point of view (and the point of view of many colleagues), the most
> important feature about 2.1 release is to be able to use the same stable
> Maven version in m2eclipse and comman
Hi there.
When deploying snapshot versions to a repository, I'll get a snapshot
version and a timestamped version put into that repository, along with the
associated update to maven-metadata.xml :
This is of the form thingy-1.0-20081021.000225-22.jar
I.E
thingy-{version}-{datestamp}-{buildnumber}
Hi there.
When deploying snapshot versions to a repository, I'll get a snapshot
version and a timestamped version put into that repository, along with the
associated update to maven-metadata.xml :
This is of the form thingy-1.0-20081021.000225-22.jar
I.E
thingy-{version}-{datestamp}-{buildnumber}
;re not using FB, they're human-creatable.
On Thu, Jun 5, 2008 at 1:00 PM, Marvin Froeder <[EMAIL PROTECTED]> wrote:
> If I will put dependencies on separated files, why use maven dependencies?
>
> VELO
>
> On Thu, Jun 5, 2008 at 8:59 AM, Nigel Magnay <[EMAIL PROTECTED]
It's not a scope issue, it's a compiler options issue.
You could just use the same mechanism that israfil flex mojo uses,
which is to utilise the .flexLib / .actionScriptProperties files in
order to determine whether to bind dependencies into the output or
not.
On Thu, Jun 5, 2008 at 12:21 PM, Ma
t.
>
> Hudson is running on Redhat linux, but I'm running on Windows and I got
> almost the exact same errors.
>
>
> -Original Message-
> From: Nigel Magnay [mailto:[EMAIL PROTECTED]
>
> Sent: Tuesday, March 18, 2008 7:52 AM
> To: Maven Developers List
>
of cases, for a start :) And
> this is a problem only when "automating" repo addition, like in case
> a).
>
> The b) and c) cases would probably make the build fail, but
> _it_does_not_ replace real Build Discovery, since it would know only
> about "touched"/
re the failures I'm getting today with 2.0.9-SNAPSHOT:
>
>
> testitMNG2861
> (org.apache.maven.integrationtests.MavenITmng2861RelocationsAndRanges)
>
> testitMNG2744
> (org
> .apache.maven.integrationtests.MavenITmng2744checksumVerificationTest)
>
> - Brett
Help...
I started to run the integration tests to work out why my patch breaks
them, and have moved on to trying to work out why my integration tests
work on some of my machines, but not others, to a bit of confusion. My
patch is in r638310
r638310 of 2.0.x,
(https://ci.sonatype.org/job/Maven-2.0
That sounds good to me, and I see where the identifiers have come in;
I think you could do without them though, and just use the repository
URI as the identifier :-
For 'external' mirrors, accessed directly and not through a repo manager:
Say you have repo1.maven.org/maven2, and global mirrors of
On Sun, Mar 16, 2008 at 10:35 PM, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>
> On 16-Mar-08, at 1:25 PM, Nigel Magnay wrote:
>
> > Have you got a description of how you think it ought to work?
> >
>
> I will do a demo sometime this week at EclipseC
On 16-Mar-08, at 11:39 AM, Nigel Magnay wrote:
>
> > I've never thought it was sane in the first place...
> >
>
> It is. Ultimately a repository manager should requires users to point
> at one URL, period. All control must reside in the repository manager
> o
I've never thought it was sane in the first place...
I don't understand why the artifact servers (archiva et al) can't just
respond in the same way that an ordinary proxy server does, without
all this mirrorOf mucking about. Working on two or three independant
projects and my settings.xml is a blo
Can anyone help answer whether I've missed some subtlety as to why a
fix like this wouldn't work (I appreciate the inner workings of maven
can be a bit complicated...) ?
On Sun, Feb 3, 2008 at 6:10 PM, Nigel Magnay <[EMAIL PROTECTED]> wrote:
> The problem is that putting it
like maybe you need to use pluginManagement in a corp pom to
> resolve this issue.
>
>
> -----Original Message-
> From: Nigel Magnay [mailto:[EMAIL PROTECTED]
> Sent: Sunday, February 03, 2008 8:44 AM
> To: dev@maven.apache.org
> Subject: MNG-3284
>
> Hi.
>
> In o
Hi.
In our work projects, we're *constantly* being bitten by the 'first
version of a plugin used wins' problem, which seems variously
described in particular MNG JIRA items, mine in particular being
MNG-3284.
I've had a go at fixing it as it didn't seem that complicated - but -
some of the commen
ew API ?
On Jan 14, 2008 1:05 PM, Nigel Magnay <[EMAIL PROTECTED]> wrote:
> Hello.
>
> I'm trying to adapt some old code from a plugin into a standalone
> project, so I've been looking at the maven Embedder. Since this seems
> to be dead in the current releases, I&#x
Hello.
I'm trying to adapt some old code from a plugin into a standalone
project, so I've been looking at the maven Embedder. Since this seems
to be dead in the current releases, I've moved to the 2.1-SNAPSHOTS.
However, some things that I used to do have changed, and I'm
experiencing the rising w
ou'll find the basic info how to handle archivedClasses as attached
> artifact and also a
> patch from Michael which generally fixes the war-overlaying.
>
> hope this is what u r looking 4
>
> LieGrü,
> strub
>
> --- Nigel Magnay <[EMAIL PROTECTED]> schrieb:
>
&g
ation makes sense to you. We use this mechanism with 3
> dependency layers and up to
> ~10 wars (to e.g. build napsterMobile), so it's a bit complicated but
> definitely works ;)
>
> LieGrü,
> strub
>
> --- Nigel Magnay <[EMAIL PROTECTED]> schrieb:
>
>
>
Hi devs - I'm hoping for a pointer or two as to how easy this might be
to implement in practice - I think it shouldn't be too hard, but I'm
not really familiar with the possibly subtle interactions.
We build many WAR files in M2. We then merge these together at the
end, in order to create an 'uber
I've had the same problem - we needed to release and 2.2-beta-1 had a
showstopper in it.
Since I'd done the work and since it's a common theme - if you add
http://mavenversionedsnapshots.googlecode.com/svn/trunk/
as a plugin repository in your pom.xml (or your mirror or whatever), and
change your p
ply to plugins only. SNAPSHOT is used in
> conjunction with a version. If you really don't care what version you
> get (curious) then use a range.
>
> -Original Message-
> From: Nigel Magnay [mailto:[EMAIL PROTECTED]
> Sent: Monday, October 29, 2007 7:33 AM
> To: Maven
I could have sworn I'd read somewhere that it was possible to use dependency
versions of LATEST, RELEASE and SNAPSHOT in a pom dependency to not have to
specify which particular version I needed.
Did I just dream that? Or does it not apply to dependencies?
we have no release. It is that simple.
>
> We need to make sure that we deliver the right features. I will not be
> happy if the new release solves things but also breaks things that
> worked before.
>
> If you want to fasten the process, join and help :)
>
> Thanks,
>
es slated for 2.2-beta-2.
>
> -john
>
> On Oct 22, 2007, at 4:26 AM, Nigel Magnay wrote:
>
> > I asked the same thing last week.. 2.2-beta-2 upgrades plexus-
> > archiver and
> > should fix PLX-344 which causes the end of our builds for machines
> > to sit
> &
I asked the same thing last week.. 2.2-beta-2 upgrades plexus-archiver and
should fix PLX-344 which causes the end of our builds for machines to sit
around looking broken for several minutes...
On 22/10/2007, Dave Hoffer <[EMAIL PROTECTED]> wrote:
>
> Any idea when maven-assembly-plugin version 2
Hi guys - it's been 6 months since the last maven-assembly-plugin release.
2.2-beta-2 upgrades plexus-archiver and should fix PLX-344 which is a
particularly niggly issue.
Is there any plan to release a new version anytime?
Sort of related to local repositories, and a thought that came back to me
after reading about separating snapshots and releases - could we do
something about caching the results of transitive dependency resolution? As
fast as XML pull parsing is, it's repeated over and over again for release
depend
[A]. IMO this is totally critical to generate auditably correct builds,
which ought to be the default. I've got 3 or 4 maven-built projects, and
it's already a bit of a nightmare - I really really don't want to be in the
situation where downloading new releases of mvn 'magically' updates plugins,
o
anism (and it's something you
could do as in a mojo), just something that becomes easier if you don't have
inconsistent repository IDs.
On 01/09/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>
>
> On 1 Sep 07, at 5:43 AM 1 Sep 07, Nigel Magnay wrote:
>
> > A couple of
A couple of really neat features, regardless of whether guids or some other
identifying mechanism is used, would be
1) ability to use zeroconf (/bonjour) style networking to automatically
configure your mirror settings
2) for repositories themselves to contain a bit more metadata about the
reposito
/08/2007, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> I already responded to this here: http://www.nabble.com/Re%3A-local-
> repositories-%28was%3A-http%3A--jira.codehaus.org-browse-MNG-3151%29-
> p12286344s177.html
>
> Cheers,
> Brett
>
> On 29/08/2007, at 4
>
> If you are knowingly doing this then I would say different settings
> via a build plan to prevent corruption or the CI mechanism serializes
> the builds.
>
How can one do this and still make use of all 8 cores to build on a
desktop machine (or all 16 on our CI server)? m2 builds could run
real
Hello
I've been using m2 for a couple of years now, worked on the odd mojo, but
have felt the urge of late to dig into the sourcecode and perhaps understand
it a bit more - if only initially to better diagnose when external tools
that make use of m2 break, what might be the source of the problem.
Here's how I deal with instances where I need a snapshot plugin in my
corp build:
1. Checkout the code for the snapshot.
2. Build it, changing the version to something like
2.0-[companyname]-svnrev
3. If I have to patch the source at all, I take the whole thing and put
it in my svn. If not, then
Dependency report broken if M1 artifacts referenced
---
Key: MSITE-85
URL: http://jira.codehaus.org/browse/MSITE-85
Project: Maven 2.x Site Plugin
Type: Bug
Reporter: Nigel Magnay
Workaround is :
true in
Documentatin points to invalid svn archive location
---
Key: MASSEMBLY-63
URL: http://jira.codehaus.org/browse/MASSEMBLY-63
Project: Maven 2.x Assembly Plugin
Type: Bug
Reporter: Nigel Magnay
Priority: Minor
Components: Plugins and Lifecycle
Versions: 2.0
Environment: Windows NT; JDK 1.5
Reporter: Nigel Magnay
I have a plugin with a component.xml described here.
I think the component.xml is correct - it certainly looks the
same as the plexus examples.
My project that uses this plugin
56 matches
Mail list logo
