On Tue, Jan 10, 2012 at 9:27 AM, Brett Porter wrote:
>
> On 10/01/2012, at 9:38 AM, Barrie Treloar wrote:
>
>> On Tue, Jan 10, 2012 at 9:00 AM, Brett Porter wrote:
>>> To the best of my knowledge it is not automatic - you need to run "mvn
>>> site-deploy" from the site checkout. My guess is some
None here
On 9 January 2012 23:44, Brett Porter wrote:
> No issues here.
>
> On 06/01/2012, at 7:52 AM, Olivier Lamy wrote:
>
>> Hello,
>>
>> Apache Maven 3.0.4-RC5 has been staged for testing purpose.
>> This is a preview (and not an official supported version) of the
>> coming 3.0.4 official re
No issues here.
On 06/01/2012, at 7:52 AM, Olivier Lamy wrote:
> Hello,
>
> Apache Maven 3.0.4-RC5 has been staged for testing purpose.
> This is a preview (and not an official supported version) of the
> coming 3.0.4 official release.
>
> The repository is available here:
> https://repository.
On 10/01/2012, at 9:38 AM, Barrie Treloar wrote:
> On Tue, Jan 10, 2012 at 9:00 AM, Brett Porter wrote:
>> To the best of my knowledge it is not automatic - you need to run "mvn
>> site-deploy" from the site checkout. My guess is someone else committed,
>> picked up your change, and pushed it.
On Tue, Jan 10, 2012 at 9:00 AM, Brett Porter wrote:
> To the best of my knowledge it is not automatic - you need to run "mvn
> site-deploy" from the site checkout. My guess is someone else committed,
> picked up your change, and pushed it.
Where is this documented?
Here http://maven.apache.org
To the best of my knowledge it is not automatic - you need to run "mvn
site-deploy" from the site checkout. My guess is someone else committed, picked
up your change, and pushed it.
On 10/01/2012, at 9:24 AM, Barrie Treloar wrote:
> It's been a long time since I've looked at this bit, and since
It's been a long time since I've looked at this bit, and since I've
got a new laptop I'm re-reading the documentation on setting things up
and finding some minor typos.
Having fixed those, I'm trying to work out how to get them uploaded.
The docs at http://maven.apache.org/developers/index.html do
Hi Dennis,
It's still here [1], it was duplicated before [2] (then caused mvn to fail)
Regards,
Hervé
[1] http://svn.apache.org/viewvc/maven/skins/trunk/maven-fluido-
skin/pom.xml?view=markup
[2] http://svn.apache.org/viewvc/maven/skins/trunk/maven-fluido-
skin/pom.xml?revision=1228915&view=m
Hi
My bad, I didn't see that it was a duplicate.
On 2012-01-09 22:57, Dennis Lundberg wrote:
> Hi Hervé
>
> After I moved the parent to a sibling-directory of the skins, each skin
> now needs to specify its SCM details. So, this will need to be put back
> again.
>
> Run a
> mvn help:effective
Hi Hervé
After I moved the parent to a sibling-directory of the skins, each skin
now needs to specify its SCM details. So, this will need to be put back
again.
Run a
mvn help:effective-pom
for the fluido-skin now and you will see that the SCM URLs are wrong.
On 2012-01-09 22:48, hbout...@apach
On 2012-01-09 21:56, Hervé BOUTEMY wrote:
> I don't know precisely if the configuration of the release plugin will be ok
> without the rc profile.
>
> But with the stagingSiteURL configuration, you can run the "Staging the
> latest
> documentation" part of the standard plugin release process [1
I don't know precisely if the configuration of the release plugin will be ok
without the rc profile.
But with the stagingSiteURL configuration, you can run the "Staging the latest
documentation" part of the standard plugin release process [1]:
cd target/checkout
mvn site site:stage-deploy -Prepo
Hello Simone,
As I said in another thread, you could remove the rc profile, I have
tried this locally. Unfortunately a bug in the Site Plugin will make
your life miserable when staging the site for 5 skins, since you need to
move the files at the remote location.
Your solution with the rc profile
On 9 January 2012 17:07, Robert Scholte wrote:
> To use Maven 2.2.1 you need at least jdk5, not the other way around (i.e. to
> use jdk5 you need at least maven 2.2.1).
> Using Maven 2.0.9 with jdk5 works just as fine.
Let me put this another way, if a plugin is using Java 1.5 code, then
in my vi
To use Maven 2.2.1 you need at least jdk5, not the other way around (i.e.
to use jdk5 you need at least maven 2.2.1).
Using Maven 2.0.9 with jdk5 works just as fine.
And there are still a lot of companies which use Maven 2, because it
works: there's no need to spend time or money to upgrade t
Well IMHO, the patch is perhaps somewhat misguided.
in m3, there will be resolution from the reactor as priority, so this
patch should only be required in m2... and in order to keep consistent
behaviour, the patch should not be switchable and the reactor search
should have priority. Other than tha
16 matches
Mail list logo
