At last, I can get profile activator to work.
However, it seems no rule when would context.getProjectDirectory()
return non-null value.
I have tried in a project with several modules, as:
project1/
module1/
module2/
module3/
module4/
module5/
Run `mvn
This is my user pom:
my.group.id
ldap-activator
0.0.1-SNAPSHOT
ldap-test
...
Maybe the profile activator should put somewhere else
I'm create a new ProfileActivator like:
@Component(role = ProfileActivator.class, hint = "ldap")
public class LdapQueryProfileActivator
implements ProfileActivator {
// ...
public LdapQueryProfileActivator() {
System.err.println("xxx");
Issue Subscription
Filter: Design & Best Practices (24 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
There is a small cluster of issues filed that can be located by looking
at http://jira.codehaus.org/browse/SUREFIRE-683
Basically there are at least three different plugins that try to find
the answer to this question "will jxr be run in this build" ?
The current solution works for maven2.x, but
On 2011-01-20 22:34, Stuart McCulloch wrote:
> On 20 January 2011 21:29, Dennis Lundberg wrote:
>
>> Hi
>>
>> I've just discovered a difference between Maven 2 and 3, and I wanted to
>> know if it is intentional or perhaps a regression.
>>
>
> intentional I believe, see
> https://cwiki.apache.or
On 20 January 2011 21:29, Dennis Lundberg wrote:
> Hi
>
> I've just discovered a difference between Maven 2 and 3, and I wanted to
> know if it is intentional or perhaps a regression.
>
intentional I believe, see
https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibil
Hi
I've just discovered a difference between Maven 2 and 3, and I wanted to
know if it is intentional or perhaps a regression.
We have our company repo defined in a profile in settings.xml. There are
2 entries inside , one for releases and one for snapshots.
In some of our products the assembly
>> Unable to find resource 'opensymphony:quartz-all:pom:1.6.2' in repository
>> central (http://repo1.maven.org/maven2)
Ask the OpenSymphony folks about this one.
>> Unable to find resource 'javax.transaction:jta:jar:1.0.1B' in repository
>> central (http://repo1.maven.org/maven2)
http://maven.a
This type of question should be addressed to the Maven user list. I've
forwarded it to there, where this thread should continue.
The answer that some things are missing in central is due to licensing. For
example, the oracle jdbc jar. They can't be added to central.
The solution is to install a re
10 matches
Mail list logo
