I do a fair bit of python tooling that invokes Java programs. Currently I
bundle the Jars with the python code; yuck. What would be neat is to have a
classpath automatically assembled by pointing to a Maven repository and passing
it a list of coordinates that are needed. The Jars would be dow
gt; On Oct 1, 2010, at 10:51 AM, Alan D. Cabrera wrote:
>
>> It's close but not exactly what I need. I don't want to maintain rules on
>> artifacts. I want to maintain restrictions between categories of artifacts.
>>
>>
>> Regards,
>> Alan
>&
the trick.
> http://maven.apache.org/enforcer/enforcer-rules/bannedDependencies.html
>
> I'm just trying to get some contributions in to maven (other enforcer
> rules) but still feel the need to say you probably should have asked
> this on the user mailing list.
>
> Rex
Is there some way to categorize jars and restrict the dependencies between
categories of those jars? At least maybe reports dependency violations?
For example let's say I have two categories, api and impl. Impl can depend on
Api but not others' impl. Api can rely on Api. When I perform a b
No forking. You can look at my setup:
git://github.com/maguro/papoose-http.git
Regards,
Alan
On Jun 2, 2010, at 10:08 AM, Brian Fox wrote:
> Is there some plugin in your build that is forking the whole build?
>
> On Wed, Jun 2, 2010 at 10:29 AM, Alan D. Cabrera wrote:
>> I
I have a root POM that defines are deploy profile that generates source,
javadoc, and signing.
When I use this profile:
mvn clean install -P deploy
My artifacts get doubly signed, e.g.
http://oss.sonatype.org/content/repositories/papoose-snapshots/org/papoose/cmpn/papoose-http/1.0-SNAPSHOT/pa
Great, thanks!
On Nov 13, 2009, at 11:55 AM, Brian Fox wrote:
In snapshots that used to be a problem but was fixed ~2.0.6ish. The
properties aren't interpolated on deploy so it works ok.
On Fri, Nov 13, 2009 at 1:23 PM, Alan D. Cabrera
wrote:
A while back this would not have been a
A while back this would not have been a safe thing to do. Will this
now work correctly?
Regards,
Alan
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
I need to programatically load jars from the local maven repository.
While the format of the repository is pretty simple I would like to be
relieved of the tedium of discovering where this local repository is
and, as an added bonus, I would love to have jars automatically
downloaded to my
Looking through NAR after an earlier thread, http://www.nabble.com/Apache-Portable-Runtime-artifacts-td20383810.html
, I am wondering how I can handle the various Linux distributions.
The only way I can think is to have the OS name be something like
SUSE-10.3 or Ubuntu-8.10.
Does anyone hav
I'm going to CC the Felix project. I'm sure their perspective will be
very useful.
On Nov 9, 2008, at 7:57 AM, Graham Leggett wrote:
Alan D. Cabrera wrote:
You bring up a good point in that it might be a good idea to
describe the target deployments. I'm sure that the APR
On Nov 9, 2008, at 6:43 AM, Max Bowsher wrote:
Alan D. Cabrera wrote:
On Nov 8, 2008, at 2:55 PM, Max Bowsher wrote:
The difficulty is that there is no standard on how to manage the
multitude of flavours of native binaries that are possible.
For example, there's architecture and OS
On Nov 9, 2008, at 4:31 AM, Graham Leggett wrote:
Alan D. Cabrera wrote:
I was thinking that the artifact name could be
apr--
e.g. apr-linux-x86_64. Or we can have a more general
apr---
where configuration is a token that represents a particular
configuration of options, e.g. apr-msdos
On Nov 8, 2008, at 2:55 PM, Max Bowsher wrote:
André Malo wrote:
* Alan D. Cabrera wrote:
On Nov 8, 2008, at 6:01 AM, Max Bowsher wrote:
Alan D. Cabrera wrote:
I would like to publish the APR artifacts into the Maven
repository,
[1]. I think that the group id should be org.apache.apr
On Nov 8, 2008, at 6:01 AM, Max Bowsher wrote:
Alan D. Cabrera wrote:
I would like to publish the APR artifacts into the Maven repository,
[1]. I think that the group id should be org.apache.apr and the
artifact id should be apr.
Does anyone have a problem with these group and artifact ids
I would like to publish the APR artifacts into the Maven repository,
[1]. I think that the group id should be org.apache.apr and the
artifact id should be apr.
Does anyone have a problem with these group and artifact ids? Does
anyone have a problem with me publishing these artifacts?
R
Has anyone compiled the Apache Portable Runtime using the native
plugin and published them somewhere?
Regards,
Alan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I'm getting a java.lang.NoClassDefFoundError when running a test and
yet, the code compiles fine. Any ideas as to what's going on? The
exact same code compiles and test fine on another box which has the
same mvn and java version.
There are no differences between 'mvn help:effective-settin
On Apr 13, 2008, at 7:20 AM, Jason van Zyl wrote:
Hi,
I have contact Leif of JSW but have yet to get a response about the
license change.
Project that start using a commercially liberal license and then
switching long into the life of a project is wrong. If you want to
do the GPL/comme
I need to copy some files into target/boot/foo before I run some unit
tests. I don't want these files to go into target/test-classes/boot/
foo.
How do I do this?
Regards,
Alan
Does anyone in maven-land know why we have to do this?
Regards,
Alan
On Oct 31, 2007, at 2:11 AM, Rick McGuire wrote:
I finally managed to get this to build, but it wasn't a pretty
process. Here were the steps:
1) I upgraded my maven version to 2.0.7.
2) Attempt to rebuild 2.0.7. This
Somehow, for my maven clean plugin, all of the maven metadata files
look like this:
org.apache.maven.plugins
maven-clean-plugin
This has been happening quite often lately whenever I do a build
under a new linux account. Does anyone know what causes this and
what is the cure, other t
On Dec 26, 2006, at 1:50 PM, Brett Porter wrote:
Hi,
I'd like to propose two things:
1) Establish a list of emeritus committers.
2) Remove inter-project commit restrictions
The first does not depend on the second. But I think the second
does depend on the first. I would like to put each to
Brett Porter wrote:
Good morning,
So, reading through the discussions on users@ and the one here
yesterday, we're getting kicked for not releasing plugins often enough
again.
Back at the start of the year I started sending out the list of
plugins to get a report on what's happening with the
+1 Nice idea.
Regards,
Alan
Jason van Zyl wrote:
Hi,
I'm sending this here as folks developing Maven projects probably all
subscribe here.
On the PMC list we've talked about setting up a sandbox that all
Apache committers would have access to so that experimentation with
Maven projects c
Brett Porter wrote:
I think the subject says it all :)
What all needs to be done? I'm not volunteering. I'm just curious.
Regards,
Alan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
David Blevins wrote:
On Jul 3, 2006, at 12:53 PM, Mohammed Nour wrote:
Hi All...
While building OEJB3.0 a missing dependency has been found, it is
xbean-finder jar artifact version 2.4-SNAPSHOT, I could not found
this jar artifact on any site listed in the main pom.xml file, I
could only fin
Yikes. That strikes me as truly scary and assumes that everyone is
running Sun compilers/JVMs. Am I misunderstanding something?
Regards,
Alan
Carlos Sanchez wrote:
I think we should add the rt.jar and tools.jar to the repo as any
other dependency, to allow building with 1.5 against 1.4 rt.j
Fabrizio Giustina wrote:
Hi,
will anybody from the maven team be at ApacheCon in Dublin? I see that
at least Jason will be there (great!), but nobody signed up for the
Hackathon yet...
just courius, I will be there at least for the first 2 days, and hope
to meet you there... (and just a few days
Mike Perham wrote:
I can't seem to commit to codehaus. Is anyone else having problems? I
thought codehaus svn was 100% restored?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Brett Porter wrote:
Hi,
I propose we focus on developing Maven 2.1 with both a mix of new
features and bug fixes.
If we identify the need for a 2.0.5, we should manually merge changes
there based on revisions from trunk, bearing in mind our new dev process.
Why would anyone terminate a bug f
Vincent Massol wrote:
-Original Message-
From: Alan D. Cabrera [mailto:[EMAIL PROTECTED]
Sent: samedi 18 mars 2006 17:50
To: Maven Developers List
Subject: Re: Jira - Issues closed without assignee
Vincent Massol wrote:
-Original Message-
From: Alan D. Cabrera [mailto
Vincent Massol wrote:
-Original Message-
From: Alan D. Cabrera [mailto:[EMAIL PROTECTED]
Sent: samedi 18 mars 2006 17:31
To: Maven Developers List
Subject: Re: Jira - Issues closed without assignee
Arnaud HERITIER wrote:
Hi guys,
I noticed that we have in maven projects
Arnaud HERITIER wrote:
Hi guys,
I noticed that we have in maven projects (particularly in m1) a lot of
issues closed (2033) but without assignee (698).
I think that it is a good practice to assign the issue to the one who
closed it (even if it's a Won't fix or duplicated status).
It's easi
What goes into:
Is there a sample working project that I can look at?
Regards,
Alan
On 2/16/2006 1:34 AM, Michael Böckling wrote:
Hi Alan ,
Next time, please write to users@maven.apache.org, this list is for
maven development!
To use Jar signing, you have to checkout the l
How do I do this?
Regards,
Alan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason van Zyl wrote, On 1/11/2006 2:36 PM:
> Howdy,
>
> It's time to release 2.0.2 so it's time to vote! Release will commend in
> 72 hours if all goes well.
>
> +1
>
Non binding +1
Thanks!
Regards,
Alan
-BEGIN PGP SIGNATURE-
Versio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Casey wrote, On 12/14/2005 11:41 AM:
> Hi all,
>
> If you've been watching this list, the users list, or JIRA, I'm sure
> you've noticed that we managed to introduce some new bugs in 2.0.1. Some
> of these are critical, and will block the use of
I think that someone mentioned that they were working on this. I am in
great need of this feature. Does anyone know the status of this?
Regards,
Alan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-
of a branch
release is always more work and error prone than "multi branch" checkins.
Just my 2 cents. :)
Regards,
Alan
- Brett
Alan D. Cabrera wrote:
Brett Porter wrote, On 11/22/2005 9:07 PM:
- use of the flying fish technique (ie bugfix only release goes over
to /br
Brett Porter wrote, On 11/22/2005 9:07 PM:
- use of the flying fish technique (ie bugfix only release goes over
to /branches/2.0.x)
* we should merge at each point release (2.0.1, 2.0.2) back to trunk
* can do interim merges if there are long time lines on those releases
It has always
I have a suggested enhancement. Maybe this is already available. Maybe
it's a bad idea. Here it is.
Frequently, I will have multiple projects that are interdependent.
Their versions will move in tandem as I change the root POM's version.
IIUC, when I change the root POM's version, I must
[X] +1 - I like it
[ ] +0 - I am not opposed, but I don't mind another technique either
[ ] -1 - I don't like it, we should have gone with _
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
Brett Porter wrote, On 9/12/2005 6:52 PM:
Hi,
I'd like to release the (overdue) Maven 2.0 Beta 1, SCM and the plugins
at Apache according to our roadmap.
Plan here:
http://docs.codehaus.org/display/MAVEN/Maven+2.0+beta+1+Release+Plan
I will continue to update it with dependencies that are ready
Brett Porter wrote, On 8/8/2005 5:15 PM:
Hi,
Alan proposed we use the standard that is used when setting up Apache
projects these days (we're still on our 2003 setup).
Here it is in summary, elaborated into a bit more detail:
1) create [EMAIL PROTECTED], scm-commits, wagon-commits,
continuum-
bin in your case :-)
SVN commits are interesting to the dev list, I would not suggest to remove them.
Cheers,
Stéphane
On 8/3/05, Alan D. Cabrera <[EMAIL PROTECTED]> wrote:
As it stands, it appears that all SVN commit messages are automatically
forwarded to the developer list. Some
As it stands, it appears that all SVN commit messages are automatically
forwarded to the developer list. Some people, like me, are not all that
interested in the commit messages. I propose that we turn off the
forwarding.
How this should be done is to automatically subscribe everyone in the
47 matches
Mail list logo
