nd smoke test the applications. Then we
> move the code to a nearly production like environment for final QA.
>
> I do not like the idea of using numbers to represent concepts. It makes
> the version numbers hard to understand and there is nothing in Maven that
> says your versions
We have recently switched to the scrum development process, and are forced
to rethink our maven versioning scheme. There will be multiple scrum teams
working with the same code-base. Each team will aim to have a release each
sprint, but occasionally a release will be planned for one sprint but
>
> 2008/2/27, Emmanuel Venisse <[EMAIL PROTECTED]>:
>> Can we see your code?
>>
>>
>> Emmanuel
>>
>>
>> On Wed, Feb 27, 2008 at 1:01 AM, kroe <[EMAIL PROTECTED]> wrote:
>>
>> >
>> > I am tinkering with the C
iwork.apps
-DarchetypeArtifactId=appArchetype
-DarchetypeVersion=1.0
-DremoteRepositories="http://username:[EMAIL
PROTECTED]/archiva/repository/releases/"
Wendy Smoak-3 wrote:
>
> On Feb 13, 2008 9:00 AM, kroe <[EMAIL PROTECTED]> wrote:
>>
>> MNG-2261 is making creating projects
, then delete it for this exact purpose and
> sent it to the list, but I don't remember details so it will be hard
> to find and easier to just re-write if you want that functionality. If
> you do this, please contribute it back via the Wiki. ;-)
>
> Wayne
>
> On 2/13/
MNG-2261 is making creating projects using an archetype difficult. I have an
archetype I created. I want the archetype:create command to download my
archetype from an internal repository. The internal repository is specified
in my settings.xml file.
Due to MNG-2261, the settings.xml reposito
Our applications are deployed to internal servers - either to JBoss as a web
application or to a directory on a specified server for exection by a
scheduling system. We have development, staging, and production
environments that we need the ability to deploy to consistenly and easily.
Maven's us
I am planning to have a corporate-pom that contains distributionManagement
information for a builds repository (all builds get dumped in there). I
can't figure out how to deploy the corporate pom though. I think the way to
do it is to upload the corporate-pom to our internal archiva repository s
We use SVN as a source control system. I am trying to implement
maven/continuum and am a bit confused. Hopefully I am missing something...
In order for continuum to find a maven2 project in the source repository and
check it out, you need an scm entry in your POM. It seems like this needs
to b
