It is. I suggest you have a look at the POM descriptor
http://maven.apache.org/ref/current/maven-model/maven.html#class_build
You'll find some information here about configuring source directories, etc.
I also strongly suggest you follow the maven conventions if you can.
SaM
On Tue, Aug 26, 2008
Is it possible to create my own directory structure? insted of
src/main/java
If Yes, please provide the steps (commands ) for this,
Thanks, In Advance
Santhosh Kumar N
+1 :)
On 26/08/2008, at 1:57 PM, John Casey wrote:
I'm okay with making the current RC a first milestone toward 2.1.0,
if we know what the endgame for 2.1.0 is. How do we know when we're
done? Also, can we focus on having a 2.1.0 GA out in the next two or
so months? It's been since April t
I'm okay with making the current RC a first milestone toward 2.1.0, if
we know what the endgame for 2.1.0 is. How do we know when we're done?
Also, can we focus on having a 2.1.0 GA out in the next two or so
months? It's been since April that we had a release, and that one had
some pretty big p
I should have read your email before I replied. I pretty much agree with
all of what you are proposing. FWIW, the bug I am working on is MNG-624
and yes, it has a ton of votes. It also addresses MNG-3057, MNG-2446,
MNG-2412 and probably several others that are related. My change is
pretty much
I'm good with making 2.0.10-RC the head of 2.1.x. I guess I'd like to
see some sort of process on 2.1 where enhancements that aren't
necessarily 100% compatible can be added so some things can be changed
before the branch is considered completely stable. By releasing 2.1.0 I
think we'd be giv
On 8/25/08, Ralph Goers <[EMAIL PROTECTED]> wrote:
>
> I'm still confused. If I had thought that it could be done that way I would
> have done it in the first place. How does that get past schema checking? Or
> are you adding it to the xsd somewhere?
The mavenImport tag is processed in the projec
I am okay with making 2.0.10 -> 2.1.0 too, but I do have to ask is
everyone up to maintaining 3 code streams (3.0, 2.0, 2.1)? In terms of
software design, the branching makes alot of sense, but due to the
amount of Critical and Blocker bugs that go into each 2.0.x release, I
don't know if that's th
Shane has reworked maven project with an eye towards these use cases.
This stuff is in maven 3.0
Sent from my iPhone
On Aug 25, 2008, at 8:26 PM, Ralph Goers <[EMAIL PROTECTED]>
wrote:
I'm still confused. If I had thought that it could be done that way
I would have done it in the first p
I'm still confused. If I had thought that it could be done that way I
would have done it in the first place. How does that get past schema
checking? Or are you adding it to the xsd somewhere?
Shane Isbell wrote:
Basically, you just put in into the pom. The id
references an external pom snippe
On 26/08/2008, at 6:44 AM, John Casey wrote:
To start, I'd personally prefer to see the code we current have in
the release process designated as 2.1.0. It's seen a lot of change
to the internal implementations, and while we've gone to great
lengths to ensure it's functionally compatible w
Why not use JIRA voting as a mechanism, officially. Or at least as a
weighting factor.
Christian.
On 25-Aug-08, at 16:44 , John Casey wrote:
Hi,
I'd like to propose that we put together a plan for the next few
releases of Maven, and also a plan for what we're going to call
them. There
Looking good in my standard environment so far.
- Brett
On 26/08/2008, at 6:15 AM, John Casey wrote:
Hi again,
One bug was identified in 2.0.10-RC10 last Friday night. This
release candidate addresses that issue. You can find it here:
http://people.apache.org/~jdcasey/stage/apache-maven/2
John,
You're doing the work for the release, so I see it as your call. I've
voiced my concern, the release is your baby.
> I've been thinking about this one all morning. When we moved the 2.0.x
> stuff in the RC branch up to beta-4, I had some serious reservations
> about moving forward with this
John,
You're doing the work for the release, so I see it as your call. I've
voiced my concern, the release is your baby.
> I've been thinking about this one all morning. When we moved the 2.0.x
> stuff in the RC branch up to beta-4, I had some serious reservations
> about moving forward with this
Hi,
I'd like to propose that we put together a plan for the next few
releases of Maven, and also a plan for what we're going to call them.
There has been quite a bit of discussion here, on IRC, and in the back
channels about how to structure this, so let's see if we can reach a
consensus.
T
Hi again,
One bug was identified in 2.0.10-RC10 last Friday night. This release
candidate addresses that issue. You can find it here:
http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC11/org/apache/maven/apache-maven/2.0.10-RC11/
Please give this a spin when you get a chance, and
I've been thinking about this one all morning. When we moved the 2.0.x
stuff in the RC branch up to beta-4, I had some serious reservations
about moving forward with this code. Brett and I (among others, I'm
sure, just don't have the thread at hand ATM) had some heated discussion
about it, and
I went through a bunch of the outstanding issues thursday (I think?) to
try to trim things down to a manageable issue-set for the next release.
I can add this one to that set, but I haven't gotten into fixing issues
yet. Right now, I'm primarily focused on releasing maven, but as soon as
that's
Hi Shane - got any answers for these?
On 09/08/2008, at 1:16 AM, Brett Porter wrote:
Thanks Shane.
I've looked over the doc and it seems to make sense. Here are some
questions (some were from earlier that I still don't quite grok).
* How is versioning handled?
* Would it be good to keep th
Hi Shane,
A few questions on this:
On 26/08/2008, at 12:26 AM, Shane Isbell wrote:
Basically, you just put in into the pom. The id
references an external pom snippet and injects it.
What does the id look like? Is the snippet a standalone file, or is it
referenced from an existing POM? And
Basically, you just put in into the pom. The id
references an external pom snippet and injects it. Right now, there is
nothing that can resolve these snippets so that's one thing that needs to be
added (I'm thinking Mercury here).
Shane
On 8/25/08, Ralph Goers <[EMAIL PROTECTED]> wrote:
>
>
>
>
2008/8/22 Mark Hobson <[EMAIL PROTECTED]>:
> Hi,
>
> I'd like to release the maven-dependency-tree shared component version
> 1.2. This release is required by m2eclipse and fixes a number of
> bugs.
>
> Staging repo:
> http://people.apache.org/~markh/staging-repo/
>
> Staging site (wait for the sy
Hi John,
On 22/08/2008, at 10:35 AM, John Casey wrote:
As far as selective merging to 2.1.x, of course we'll keep things
like Dan's change, but where does that leave all of the stabilizing
work on the RC branch? Most of the substantive changes in the RC
branch is also in the 2.1.x branch,
+1
2008/8/25 Arnaud HERITIER <[EMAIL PROTECTED]>
> +1
>
> Arnaud
>
> On Mon, Aug 25, 2008 at 10:41 AM, Lukas Theussl <[EMAIL PROTECTED]>
> wrote:
>
> > +1
> >
> > -Lukas
> >
> >
> >
> > Vincent Siveton wrote:
> >
> >> Hi,
> >>
> >> We solved more than 30 issues:
> >>
> >>
> http://jira.codehaus.o
+1
Arnaud
On Mon, Aug 25, 2008 at 10:41 AM, Lukas Theussl <[EMAIL PROTECTED]> wrote:
> +1
>
> -Lukas
>
>
>
> Vincent Siveton wrote:
>
>> Hi,
>>
>> We solved more than 30 issues:
>>
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14120&styleName=Html&projectId=11138
>>
>> There are st
+1
-Lukas
Vincent Siveton wrote:
Hi,
We solved more than 30 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14120&styleName=Html&projectId=11138
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11138&status=1
Ralph Goers wrote:
Ralph Goers wrote:
Ralph Goers wrote:
Shane Isbell wrote:
I've been refactoring more of the project builder code and
encountered a
rule that if a dependencyManagement/dependencies/dependency element
has
type=pom and scope=import, the dependency management section o
De Smet Ringo wrote:
> I figured it out! I have the maven-plugin-plugin both as a build plugin
> and a reporting plugin and it seems I have to configure the goal prefix
> in both sections of my plugin POM.
You shouldn't need to configure the goal prefix twice. Just as my example
shows, it should
29 matches
Mail list logo
