Ok, I switched to a local staging directory and that URL
(matzew::default::file:/trinidad-stage) worked.
But. I figured out another bug in Maven. I searched the maven list
and came to an issue that another user was also seeing. The source-jar
build was skipped, after the size has reached 4
Hi,
I finally managed to get some release artifacts published to a stage
repo. I used my private Apache account for that ([1]).
Please take a look at the 1.0.0-incubating artifacts and vote if we
should take these file to ask the Incubator PMC for approval
[X] +1 (Binding) for PPMC members only
[ ] +1 for community members who have reviewed the bits
[ ] +0
[ ] -1 for fatal flaws that should cause these bits not to be released,
and why..
Hi Martin,
see inline for some comment
On 2/10/07, Martin van den Bemt [EMAIL PROTECTED] wrote:
In short : according to me they are.. Any feedback and additions appreciated..
On note : I like to
see that at least the plugins get a release before we start a vote on dev (and
I expressed below
found it
http://mojo.codehaus.org/rat-maven-plugin/
looking later at it
-Matthias
On 2/14/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Hi Martin,
see inline for some comment
On 2/10/07, Martin van den Bemt [EMAIL PROTECTED] wrote:
In short : according to me they are.. Any feedback and
[ ] +1 (Binding) for PPMC members only
[x] +1 for community members who have reviewed the bits
[ ] +0
[ ] -1 for fatal flaws that should cause these bits not to be released,
and why..
Wish for future releases:
Add
Aren't you a mentor ?
On 2/14/07, Manfred Geiler [EMAIL PROTECTED] wrote:
[ ] +1 (Binding) for PPMC members only
[x] +1 for community members who have reviewed the bits
[ ] +0
[ ] -1 for fatal flaws that should cause these bits not to be
ah, PMC-chair
I was thinking you actually are a member.
Jim's page clarifies this:
http://people.apache.org/~jim/committers.html
-M
On 2/14/07, Manfred Geiler [EMAIL PROTECTED] wrote:
panic-mode
Am I ?!
A look at http://incubator.apache.org/projects/adffaces.html tells me I'm not.
/panic-mode
Yeah, thanks anyway Jeanne. Adam is on the ball. :)
Jeanne Waldman wrote:
Oh, I see Adam already did this.
Thanks Adam.
Jeanne Waldman wrote:
Scott,
I'll do my best to review your patches and check them into trunk and
the JSF 1.2 branch.
It would be great if someone else can give their
Hi,
I updated my trunk and I'm having problems, and I'm wondering if it is
because of one of these patches.
To reproduce:
- run a demo, like index.jspx
--- the page comes up fine, but this renders on the page:
com.sun.faces.saveStateFieldMarker
I see these warnings:
Feb 14, 2007
The reason I ask is that I was getting a similar error (to the
StateFieldMarker markup) when using the 1.2 branch, in the Portal Proof
of Concept environment, with some of my extension involved. But I
tracked this down to be an issue with the bridge I was using. I did NOT
see this behavior
Jeanne,
You're not using this in a Portal POC correct?
Scott
Jeanne Waldman wrote:
Hi,
I updated my trunk and I'm having problems, and I'm wondering if it is
because of one of these patches.
To reproduce:
- run a demo, like index.jspx
--- the page comes up fine, but this renders on the
No, I'm not running in a Portal.
I'll look into it some. If anyone else sees this issue, let me know.
Jeanne
Scott O'Bryan wrote:
The reason I ask is that I was getting a similar error (to the
StateFieldMarker markup) when using the 1.2 branch, in the Portal
Proof of Concept environment, with
+1.
Thanks,
Gab
On 2/14/2007 2:13 AM, Matthias Wessendorf wrote:
Hi,
I finally managed to get some release artifacts published to a stage
repo. I used my private Apache account for that ([1]).
Please take a look at the 1.0.0-incubating artifacts and vote if we
should take these file to ask
Jeanne,
I was looking at the trunk and it appears that ADFFACES-379 was not
applied to trunk and ADFFACES-374 is 1.2 only. So no, this issue is not
related being that none of the patched code is actually in the trunk. :)
After you figure out the issue, can you look at applying ADFFACES-379
I did a clean build and it works fine now. Something must have gotten
corrupted.
I'll apply your 379 to trunk.
- Jeanne
Scott O'Bryan wrote:
Jeanne,
I was looking at the trunk and it appears that ADFFACES-379 was not
applied to trunk and ADFFACES-374 is 1.2 only. So no, this issue is
not
Oh cool, thanks Jeanne. Unlike the 1.2 branch, the patch should apply
cleanly to the trunk. Adam did all the hard work. :)
Scott
Jeanne Waldman wrote:
I did a clean build and it works fine now. Something must have gotten
corrupted.
I'll apply your 379 to trunk.
- Jeanne
Scott O'Bryan
Hey everyone,
I really don't like very long files, and especially the long css-files.
So I was wondering: why don't we split up the css-file into multiple
files: one components-shared.css, and one file for each component. I
think that this will create more overview, and it separates things a
18 matches
Mail list logo
