On Tue, Nov 17, 2009 at 6:41 PM, Henrib wrote:
>
> Tried an RC3 after cleansing the xdoc related elements.
> From a clean svn checkout, the 'mvn site' works as expected.
>
> Using the manual procedure, generated
> http://people.apache.org/~henrib/jexl-2.0rc3/site/staging/ which is styled
> correct
exl-2.0rc3/site
>
Similar symptoms in http://jira.codehaus.org/browse/MSITE-404 ...
--
View this message in context:
http://old.nabble.com/Help-cutting-JEXL-2.0-RC1-needed-tp26339499p26396488.html
Sent from the Commons - Dev mailing list arc
Hints welcome as usual.
--
View this message in context:
http://old.nabble.com/Help-cutting-JEXL-2.0-RC1-needed-tp26339499p26395243.html
Sent from the Commons - Dev mailing list archive at Nabble.com.
-
To unsubscribe, e-mail:
the navigation.xml...
This might be one of the causes as explained in
http://maven.apache.org/guides/mini/guide-site.html .
I'll dig into this.
--
View this message in context:
http://old.nabble.com/Help-cutting-JEXL-2.0-RC1-needed-tp26339499p26385994.html
Sent from the Commons
; navigation.xml,changes.xml
>
>
>
>
I removed this for RC2 trying to reduce entropy...
--
View this message in context:
http://old.nabble.com/Help-cutting-JEXL-2.0-RC1-needed-tp26339499p26385813.htm
p://maven.apache.org/developers/release/apache-release.html
http://commons.apache.org/building.html
http://commons.apache.org/releases/prepare.html
http://commons.apache.org/releases/release.html
http://wiki.apache.org/commons/CreatingReleases
Thanks
Henrib
--
View this message in context:
http://old.nabble.co
>>> 'mvn site' locally generates a different version than the one that ends up
>>> being published; the local version does generate the reports menu & seems
>>> to be styled correctly but the published version lacks the reports and
>>> styling is n
the local version does generate the reports menu & seems
> >> to be styled correctly but the published version lacks the reports and
> >> styling is non-existent...
> >> Anyone with a similar
rate the reports menu & seems
>> to be styled correctly but the published version lacks the reports and
>> styling is non-existent...
>> Anyone with a similar experience ?
>>
>
> --
> View this message in context:
> http://old.nabble.com/Help-cutt
orts menu & seems
> to be styled correctly but the published version lacks the reports and
> styling is non-existent...
> Anyone with a similar experience ?
>
--
View this message in context:
http://old.nabble.com/Help-cutting-JEXL-2.0-RC1-needed-tp26339499p26379919.html
Sent from the
-existent...
Anyone with a similar experience ?
--
View this message in context:
http://old.nabble.com/Help-cutting-JEXL-2.0-RC1-needed-tp26339499p26375531.html
Sent from the Commons - Dev mailing list archive at Nabble.com.
-
To
this finally made it work.
I'll send out the vote momentarily.
Thanks to all for helping out!
--
View this message in context:
http://old.nabble.com/Help-cutting-JEXL-2.0-RC1-needed-tp26339499p26362268.html
Sent from the Commons - Dev mailing list archive at Nabble.com.
On Sun, Nov 15, 2009 at 9:21 AM, Henrib wrote:
>
>
> Using the trunk in the tag and -Dpassword allowed to successfully
> prepare!
Progress. The section should have trunk URLs (in trunk :-) so
that must have got out of sync somewhere along the way here.
> The release:perform is getting stuck
ore a few days with log4php.
>
> However, I also figured out that I need to -Dpassword to make this work
> correctly - did you manage it to run a commit with certificate?
>
> Cheers
> Christian
>
>
--
View this message in context:
http://old.nabble.com
>
>
> [INFO] Tagging release with the label JEXL_2_0_RC1...
> [INFO] Executing: /bin/sh -c cd
> /Users/henri/Java/apache-commons/rc1/commons/jexl-2.0 && svn
> --non-interactive copy --file
>
> /var/folders/Ya/YaSJZzgsHu4O4NXovx-nNE+++TI/-Tmp-/maven-scm-1545582656.commit
> --revision 836226
> https:
r/jexl/tags/JEXL_2_0_RC1
The source & destination of the svn copy are the same...
I suspect the pom.xml should carry somewhere the 'trunk' information; may be
the should mention the trunk rather than RC1 ?
Hints welcome.
Henrib
--
View this message in context:
http://old.nabble
sebb wrote:
> On 14/11/2009, Christian Grobmeier wrote:
>> >
>> > > I'm sure glad there is help; there are a few project that are just going
>> > /
>> > > went through that process (commons-exec for instance) . Is there anyone
>> > > involved willing to share their successful publishing proce
On 14/11/2009, Christian Grobmeier wrote:
> >
> >
> > > I'm sure glad there is help; there are a few project that are just going
> > /
> > > went through that process (commons-exec for instance) . Is there anyone
> > > involved willing to share their successful publishing process ?
> >
> >
>
>
> > I'm sure glad there is help; there are a few project that are just going
> /
> > went through that process (commons-exec for instance) . Is there anyone
> > involved willing to share their successful publishing process ?
>
> We definitely need to do that and it is on my todo list to documen
Henrib wrote:
> Thanks Phil.
> My first hurdle is the signing part which I'm just discovering and have yet
> to understand...
> And information is hard to find: the public_html directory is not the most
> documented thing you ought to know. What should be in there exactly ?
As Rahul pointed out, p
Attempts at answering any specific questions below ...
On Fri, Nov 13, 2009 at 6:11 PM, Henrib wrote:
>
> Thanks Phil.
> My first hurdle is the signing part which I'm just discovering and have yet
> to understand...
The m2 gpg-plugin should do it fairly effortlessly (once its set up,
which may
help you through the M2 release
> around Saturday or Sunday evening (e.g. 22:00 CET+1)
>
> Cheers
>
> PS: I remember my first release too well ... ;-)
>
>
--
View this message in context:
http://old.nabble.com/Help-cutting-JEXL-2.0-RC1-needed-tp26339499p26345266.html
Se
ers/release/apache-release.html
> ...
>
--
View this message in context:
http://old.nabble.com/Help-cutting-JEXL-2.0-RC1-needed-tp26339499p26345087.html
Sent from the Commons - Dev mailing list archive at Nabble.com.
-
tory/...
> and then scp them to my home directory and unpack them in public_html.
>
> Phil
>
>
--
View this message in context:
http://old.nabble.com/Help-cutting-JEXL-2.0-RC1-needed-tp26339499p26345042.html
Sent from the Commons - Dev
On Fri, Nov 13, 2009 at 11:38 AM, Henrib wrote:
>
> I'm stuck trying to create an RC1 for JEXL-2.0.
> I've followed each step of the procedure described at
> http://wiki.apache.org/commons/CreatingReleases .
>
> When performing the mvn -prc release:prepare , it gets stuck on [gpg:sign
> {execution
Hi Henrib,
if needed I can lend you a hand and help you through the M2 release
around Saturday or Sunday evening (e.g. 22:00 CET+1)
Cheers
PS: I remember my first release too well ... ;-)
Henrib wrote:
> Thanks for the info; not sure how to perform step 5 though...
> Trying to cut a release is
Henrib wrote:
> Thanks for the info; not sure how to perform step 5 though...
> Trying to cut a release is a tad stressfull for a newbie. :-)
The stress never goes away, but neither does the help :)
>
> Niall Pemberton-2 wrote:
>> ...
>> 5) Upload the artifacts for review
>> ...
>>
>
I always ju
Thanks for the info; not sure how to perform step 5 though...
Trying to cut a release is a tad stressfull for a newbie. :-)
Niall Pemberton-2 wrote:
>
> ...
> 5) Upload the artifacts for review
> ...
>
--
View this message in context:
http://old.nabble.com/Help-cutting-JEXL
HotSpot(TM) Client VM (build 1.5.0_19-137, mixed mode, sharing)
> Hornet:jexl-2.0 henri$ uname -a
> Darwin Hornet.local 10.2.0 Darwin Kernel Version 10.2.0: Tue Nov 3 10:37:10
> PST 2009; root:xnu-1486.2.11~1/RELEASE_I386 i386
> Hornet:jexl-2.0 henri$
> )
>
>
> --
> View
win Kernel Version 10.2.0: Tue Nov 3 10:37:10
PST 2009; root:xnu-1486.2.11~1/RELEASE_I386 i386
Hornet:jexl-2.0 henri$
)
--
View this message in context:
http://old.nabble.com/Help-cutting-JEXL-2.0-RC1-needed-tp26339499p26339499.html
Sent from the Commons - Dev mail
30 matches
Mail list logo
