Issue Subscription
Filter: Design & Best Practices (29 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-3313NetBeans projects, more than ant project, more than fre
I think we should maintain the current functionality of a default deactivating
when another profile in the pom is activated until there is a syntax to perform
the same. I have often in the past done things like: (pseudo pom code)
all
true
a
b
c
...
a
a
Etc and the act
FYI, I just merged version comparison improvement to artifact trunk.
2.1.x ITs are ok, both on my machine and on Sonatype's CI server
I hope everything is ok for everybody
Don't hesitate to ring me if anything goes wrong
regards,
Hervé
Le jeudi 01 mai 2008, Hervé BOUTEMY a écrit :
> Kenney sta
The Maven team is pleased to announce the release of the Maven Surefire,
version 2.4.3.
Maven Surefire is used during the "test" phase of the build lifecycle to
execute your unit tests. It supports JUnit 3 & 4 as well as TestNG, and
generates TXT, XML and HTML reports.
http://maven.apache
John Casey wrote:
The activeByDefault flag was originally designed to allow profiles to
work as a group, with a default selection. Obviously, it's an incomplete
design, since it doesn't allow for profiles that _aren't_ part of that
grouping to be activated/deactivated independently. As for the
Ralph Goers wrote:
Paul Gier wrote:
I would like to bring up a couple of issues related to profile
activation and deactivation. While working on MNG-3545 I noticed some
cases where the current behaviour might be improved.
1. What is the correct behaviour when there is more than one
activ
D/E were meant to work in cases where the - leading character might
be a problem. If it's never a problem, we don't need them. If the
only argument to the -P option can be something like "-
myProfile" (leading dash) then we have no need for it...and the !
notation might make this even better
2.0.x and 2.1 work the same after your change. "+" means activate and "-" means
deactivate. I'm guessing it was just a typo in 2.1 that had them reversed.
What's the reason for the D: and E: syntax? Do we need these if +,-,!, can be
used?
John Casey wrote:
I looked at the logic for +/- the
No one can dispute the nice things that profiles let us accomplish in
terms of toggling on functionalities...
But I wonder much this will impact build reproducibilityespecially
given the existence of profiles in the settings.xml file. It is
already a source of minor pain where people need to
I looked at the logic for +/- the other day (when I added E: and D:,
fwiw), and the logic was backward, IIRC...I fixed it in 2.1, but it
may still be broken in 2.0.x, not sure...
-john
On May 14, 2008, at 5:44 PM, Brian E. Fox wrote:
Need to think about 1& 2 some more but:
3. There was a
The activeByDefault flag was originally designed to allow profiles to
work as a group, with a default selection. Obviously, it's an
incomplete design, since it doesn't allow for profiles that _aren't_
part of that grouping to be activated/deactivated independently. As
for the default profil
+1. My first reaction though was the thought, what should -P-profile
do? Is it confusing not to have it if + is supported? Would it be the
same as -P!profile?
Bernhard David wrote:
would it be possible to have "-Pprofile" work as usual (activate
profile, deactivate defaults) but "-P+profile
Paul Gier wrote:
I would like to bring up a couple of issues related to profile
activation and deactivation. While working on MNG-3545 I noticed some
cases where the current behaviour might be improved.
1. What is the correct behaviour when there is more than one
activeByDefault profile a
Same use case here.
IMHO having a distinction between "-P profile" and "-P +profile" is
acceptable. "-P profile" may work as it does today (specify the exact list
of profiles, whith auto-disabled default ones). For backward compatibility,
but also to enable exclusive profiles switching.
2008/5/1
Would a concept of profile groups help to determine which profiles are
meant to be mutually exclusive?
I use mutually exclusive profiles for different deployment
configurations, for example development and production. By default,
the development profile is actived by default, so currently
-Pprodu
15 matches
Mail list logo