Hi,
the ASF master-pom does contain a _regular_ snapshot repo (linked to
the (new) nexus repo), see:
https://svn.apache.org/repos/asf/maven/pom/trunk/asf/pom.xml
*snip*
repository
idapache.snapshots/id
nameApache Snapshot Repository/name
Hi,
the master pom still contains this section:
ciManagement
systemcontinuum/system
urlhttp://myfaces.zones.apache.org:8080/continuum/url
notifiers
notifier
typemail/type
configuration
[
https://issues.apache.org/jira/browse/TRINIDAD-1953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12928560#action_12928560
]
Matthias Weßendorf commented on TRINIDAD-1953:
--
I did
a) clean ups of the
hi,
thx - i was going to write the same mail.
+1 for changing it.
regards,
gerhard
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
2010/11/5 Matthias Wessendorf mat...@apache.org
Hi,
the
Committed revision 1031524.
On Fri, Nov 5, 2010 at 12:22 PM, Gerhard gerhard.petra...@gmail.com wrote:
hi,
thx - i was going to write the same mail.
+1 for changing it.
regards,
gerhard
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and
Hi,
the TRUNK has this dependency
portlet-bridge.version1.0.0-beta/portlet-bridge.version
which causes some *problems* when you delete your entire REPO.
Why?
It's OLD portlet-bridge-master-pom-2 has:
a) overridden the repositories section ([1])
b) dependency to myfaces-6 (Trinidad has against
We keep that inside of our Trinidad pom b/c that way we don't force all others
to go with *snapshots*, of plugins.
Trinidad's maven plugins are a separate project, therefore it is needed.
Will update the POM with a comment.
-M
On Fri, Nov 5, 2010 at 9:49 AM, Matthias Wessendorf
If you are wondering, why this failure is here:
http://jira.codehaus.org/browse/MENFORCER-110
(looks like it's fixed in a few days...)
.Matthias
On Fri, Nov 5, 2010 at 8:42 AM, Apache Hudson Server
hud...@hudson.apache.org wrote:
See
Matthias,
Just wanted to say thanks for all the work. Cleaning up the pom is no fun
especially when there were complications, but I appreciate the effort.
-Andrew
2010/11/5 Matthias Weßendorf (JIRA) dev@myfaces.apache.org
[
You are welcome!
It was needed, and I am actually happy that's almost working (see my
other 'rant' email) :)
-Matthias
On Fri, Nov 5, 2010 at 4:37 PM, Andrew Robinson
andrew.rw.robin...@gmail.com wrote:
Matthias,
Just wanted to say thanks for all the work. Cleaning up the pom is no fun
Hi,
https://svn.apache.org/repos/asf/myfaces/portlet-bridge/core/trunk/pom.xml
can we move that to
parent
artifactIdportlet-bridge-master-pom/artifactId
groupIdorg.apache.myfaces.portlet-bridge/groupId
version3/version
/parent
to version '4' (or even '5-SNAPSHOT') ?
-Matthias
Hi
I think it could be useful to include it on myfaces master pom. After all,
on myfaces
there exists multiple plugins that should be updated from time to time.
regards,
Leonardo Uribe
2010/11/5 Matthias Wessendorf mat...@apache.org
We keep that inside of our Trinidad pom b/c that way we
No, I think we don't want every plugin's (all the maven plugins etc)
on our trunk build...
-M
On Fri, Nov 5, 2010 at 5:30 PM, Leonardo Uribe lu4...@gmail.com wrote:
Hi
I think it could be useful to include it on myfaces master pom. After all,
on myfaces
there exists multiple plugins that
What I understand is add that entry to myfaces master pom allow to use
snapshot versions temporally for maven plugins, but does not force to use
it. Some days ago I did a svn checkout of a myfaces project and I notice
that
myfaces-builder-plugin was not downloaded from internet, but that one
was
panelPageSkinDemo - the skin picker choice is not changing the skin
---
Key: TRINIDAD-1955
URL: https://issues.apache.org/jira/browse/TRINIDAD-1955
Project: MyFaces Trinidad
View root caching causes transient property keys to be kept for multiple
requests
-
Key: TRINIDAD-1956
URL: https://issues.apache.org/jira/browse/TRINIDAD-1956
Project:
I'm trying to understand why the require-bundle header is in the api bundle.
This is a pretty bizarre thing to do in what I've seen of osgi.
I took it out and geronimo-tomcat appears to work OK. Maybe because this is
because geronimo has a somewhat extended thread context classloader, but
I think a plugin snapshot repo is not in the asf master pom because using
snapshot plugins is not something the maven devs want to encourage. Why does
myfaces need a snapshot plugin? I'd recommend putting the plugin repo entry
near the use of the plugin so it can be removed easily when the
On Fri, Nov 5, 2010 at 7:03 PM, David Jencks david_jen...@yahoo.com wrote:
I think a plugin snapshot repo is not in the asf master pom because using
snapshot plugins is not something the maven devs want to encourage.
Agreed - said that later on, too
Why does myfaces need a snapshot plugin?
Hi
Well, in myfaces there are projects that use plugins hosted in myfaces. For
example, myfaces-builder-plugin is required to build myfaces-core. In some
moments, it appear bugs on core that require some changes on
myfaces-builder-plugin, so in those moments we need a plugin snapshot, just
while
[
https://issues.apache.org/jira/browse/TRINIDAD-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Robinson resolved TRINIDAD-1956.
---
Resolution: Fixed
Fix Version/s: 1.2.15-core
Hi,
today I did some maven/pom clean up and hudson server related work.
As part of that the nightly builds for all 'supported' Trinidad
versions are back:
See here for example:
https://repository.apache.org/content/repositories/snapshots/org/apache/myfaces/trinidad/trinidad-api/
Next (as I did
[
https://issues.apache.org/jira/browse/MYFACES-2944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe resolved MYFACES-2944.
-
Resolution: Fixed
Assignee: Leonardo Uribe (was: Jakob Korherr)
Make those
[
https://issues.apache.org/jira/browse/MFCOMMONS-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe resolved MFCOMMONS-20.
-
Resolution: Fixed
Fix Version/s: 1.0.1-SNAPSHOT
Add mc:outputClientId
[
https://issues.apache.org/jira/browse/MYFACES-2951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe resolved MYFACES-2951.
-
Resolution: Fixed
Fix Version/s: 2.0.3-SNAPSHOT
[PERF] enhance scanning for
Remove the feature that puts Tobago in debugMode with locale to-ba-go
---
Key: TOBAGO-938
URL: https://issues.apache.org/jira/browse/TOBAGO-938
Project: MyFaces Tobago
[
https://issues.apache.org/jira/browse/TOBAGO-938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Udo Schnurpfeil resolved TOBAGO-938.
Resolution: Fixed
Remove the feature that puts Tobago in debugMode with locale to-ba-go
Descriptions of components, attributes, etc. are missing in taglib.xml files
generated by MyFaces Builder Plugin
Key: MYFACES-2962
URL:
Update shale-test dependency with myfaces-test
--
Key: MFCOMMONS-21
URL: https://issues.apache.org/jira/browse/MFCOMMONS-21
Project: MyFaces Commons
Issue Type: Improvement
Reporter:
[
https://issues.apache.org/jira/browse/MFCOMMONS-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe resolved MFCOMMONS-21.
-
Resolution: Fixed
Fix Version/s: 1.0.1-SNAPSHOT
Update shale-test dependency
Set default templates automatically when jsfVersion is 20 or 2.0 with
myfaces-builder-plugin
Key: MYFACES-2963
URL: https://issues.apache.org/jira/browse/MYFACES-2963
[
https://issues.apache.org/jira/browse/MYFACES-2963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe resolved MYFACES-2963.
-
Resolution: Fixed
Fix Version/s: 2.0.3-SNAPSHOT
Set default templates
32 matches
Mail list logo
