what about the shortcoming described in the "Why there are no dependency
properties in Maven2" article?
Notice we're back at a the POM model question (+ compatibility and so on) [1]
But let's start with understanding the need and how it can scale or not
Regards,
Hervé
[1]
https://cwiki.apache
ideally, yes, I would expect to get user properties from dependencies as
part of standard maven api.
IIRC it was just a string-only property bag multimap in maven 1.x
but I am not even asking that, I can parse pom.xml again in my plugin
and find what I need.
where I need your help is not to enfo
if we add such relaxed load during build, how do you expect to retrieve the
info?
I suppose you'll need an API to catch the info
Regards,
Hervé
Le jeudi 4 avril 2013 10:03:25 Andrei Pozolotin a écrit :
> *Wayne*
>
> 1) in this case "I choose madness" :-)
>
> 2) here is my request:
yes:
http://docs.codehaus.org/display/MAVENUSER/FAQs-1#FAQs-1-WhytherearenodependencypropertiesinMaven2
Original Message
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
From: Jason van Zyl
To: Maven Developers List
Date: Thu 04 Apr 2013 12:47:18 PM CDT
> Are you talking about properti
Are you talking about properties on dependencies like we used to have in Maven
1.x?
On Apr 4, 2013, at 1:28 PM, Andrei Pozolotin wrote:
>Wayne and ALL:
>
>Thank you very much for considering this request, I got my answer.
>
>Does it make sense to file a jira at this point?
>
>
Wayne and ALL:
Thank you very much for considering this request, I got my answer.
Does it make sense to file a jira at this point?
Andrei
Original Message
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
From: Wayne Fay
To: Maven Developers List
Date: Thu 04 Apr 201
> to be able to annotate with user properties - the kind
> of constrains I would like maven to remove in 3.1.0.
Doubtful to be removed in 3.1.0.
> So: can I please respectfully request a formal PMC vote on my change
> request or should I just go away and leave you all alone? :-)
Tamás
Thank you very much for the complete nexus plugin example, it seems
like one-to-one mapping to our osgi problem domain.
I now totally get what you are saying, and yes, we could use the
approach similar to nexus plugin declarations in the karaf maven plugin.
However
got it, thank you. I still would like you to conciser my change request.
Original Message
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
From: Fred Cooke
To: Andrei Pozolotin
Cc: Maven Developers List
Date: Thu 04 Apr 2013 11:14:46 AM CDT
> I mean, you can grab any array pom propert
Michael:
re "classifiers or build qualiafiers" - these are not variations on
dependency
this is same dependency, but in different poms this dependency have
different custom property.
think of it like @Inject annotation in guice
Thank you,
Andrei
Origina
Andrei,
Wayne is right, the dependencies (or even depMgt) section is NOT a place
for information like these.
This is Karaf plugin specific, it must go into plugin configuration.
As _similar_ example, here is a quite simple example, but with very similar
intention (true, the amount of params here
I mean, you can grab any array pom properties by index in a variable, why
not do it in code, if you don't want duplication. This way the fragility is
limited to index and easily fixed if it gets messed up by an added
dependency.
http://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuide
http:
Am 2013-04-04 15:57, schrieb Andrei Pozolotin:
Hervé:
thank you for taking the time to respond.
issue at hand:
karaf
http://karaf.apache.org/
has features.xml, which are built from pom.xml
http://karaf.apache.org/manual/latest-2.3.x/users-guide/provisioning.html
what is missing from maven is
Fred
I am sorry I do not understand what you mean. Can you please clarify?
The only reason am I bothering people on maven dev list is because
maven refuses to work at all when I add custom xml entries to the
.
I would assume it would be easy change just to ignore things ma
Can you not programatically access the dependencies by index? Sure it would
be fragile to dep order changes, but it would not be duplication. +1 to
everything Wayne said.
On Thu, Apr 4, 2013 at 5:03 PM, Andrei Pozolotin wrote:
> *Wayne*
>
> 1) in this case "I choose madness" :-)
>
>
*Wayne*
1) in this case "I choose madness" :-)
2) here is my request:
please provide an option to modello or whoever is enforcing strict
xml model in maven
to relax the rules, so people can use maven they way it fits them,
while enforcing the rules by default.
Tha
> the way I understand your suggestions is essentially I must duplicate
> configuration:
Yes, just like you do with the other plugins mentioned.
Wayne
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional com
Wayne:
the way I understand your suggestions is essentially I must duplicate
configuration:
1) first I have to mention the , because I need the dependency
2) second, I need some extra entry somewhere to map same to
custom properties.
am I getting you right?
Andrei.
Original Message
> what is missing from maven is the ability to communicate arbitrary
> custom attributes
> on per-dependency basis, such as:
>
> provide osgiStartLevel value, to specify to osgi runtime bundle start level:
...
> or provide karafBootInstall flag, to specify that karaf runtime should
> install this d
Hervé:
thank you for taking the time to respond.
issue at hand:
karaf
http://karaf.apache.org/
has features.xml, which are built from pom.xml
http://karaf.apache.org/manual/latest-2.3.x/users-guide/provisioning.html
what is missing from maven is the ability to communicate arbitrary
custom attr
20 matches
Mail list logo
