Re: [vote] Release Cocoon 2.2-final
Sylvain Wallez wrote: Carsten Ziegeler wrote: Luca Morandini wrote: Reinhard Poetz wrote: I've prepared the artifacts for the release of Cocoon 2.2 final. There is much room for improvement in the doc though: don't you think it should be improved before release ? It would be great to have better docs, but honestly who is going to write them? We can either release with the docs we have or wait forever for better docs and never release. From these two choices I prefer the first one. Anything between these two extremes is imho not going to happen. We might not get some new users because of bad docs, but we might get people really interested in a new Cocoon. If we wait for better docs we loose everyone as we never release. Yup. And add to this the fact that doc lifecycle is different from the software lifecycle, since there is no doc releases, but a continuous improvement. Sorry, I can't agree. Cocoon still has the same fault as many open-source products: A lack of documentation. I don't know if GSoC is for docs, too, but it is really, really necessary to improve docs. It's still the same Catch-22: To write docs you need to understand the developed, to understand the developed you need the docs, ... Writing docs does belong to development, even when it seems to be at a kindergarden level for newbies! Just my 0,02 CHF Florian
Re: [vote] Release Cocoon 2.2-final
Carsten Ziegeler wrote: Luca Morandini wrote: Reinhard Poetz wrote: I've prepared the artifacts for the release of Cocoon 2.2 final. There is much room for improvement in the doc though: don't you think it should be improved before release ? It would be great to have better docs, but honestly who is going to write them? We can either release with the docs we have or wait forever for better docs and never release. From these two choices I prefer the first one. Anything between these two extremes is imho not going to happen. We might not get some new users because of bad docs, but we might get people really interested in a new Cocoon. If we wait for better docs we loose everyone as we never release. Yup. And add to this the fact that doc lifecycle is different from the software lifecycle, since there is no doc releases, but a continuous improvement. Sylvain -- Sylvain Wallez - http://bluxte.net
Re: [vote] Release Cocoon 2.2-final
Luca Morandini wrote: Reinhard Poetz wrote: I've prepared the artifacts for the release of Cocoon 2.2 final. There is much room for improvement in the doc though: don't you think it should be improved before release ? It would be great to have better docs, but honestly who is going to write them? We can either release with the docs we have or wait forever for better docs and never release. From these two choices I prefer the first one. Anything between these two extremes is imho not going to happen. We might not get some new users because of bad docs, but we might get people really interested in a new Cocoon. If we wait for better docs we loose everyone as we never release. Carsten -- Carsten Ziegeler [EMAIL PROTECTED]
Re: [vote] Release Cocoon 2.2-final
Reinhard Poetz wrote: Luca Morandini wrote: Reinhard Poetz wrote: I've prepared the artifacts for the release of Cocoon 2.2 final. There is much room for improvement in the doc though: don't you think it should be improved before release ? What's your plan? Well, let's wargame the thing: 1) The community releases 2.2. 2) Hopefully, a lot of people would download it and try the tutorials, (which are good) and people would find it easy to get into Cocoon. 3) A few people would venture deeper, looking at the components' doc and trying things not covered by the tutorials (like I did). 4) They would find that many components have no doc available (though most are unchanged from 2.1) and some doc is outdated (for instance, I had to fix the CForms sample, otherwise it would not have worked in 2.2). 5) Some of them would find the answers they need in the Javadoc, or send messages to the list, or look into the source code. 6) Some of them, regretfully, would simply find Cocoon too hard to learn and drop it. Now, I'd try to avoid people doing 6 by combing the doc and setting it on a par with the 2.1 doc. Actually, since it took so long in the making, I suspect people expect a polished product, in both code and doc. On a more general note, it would be nice to send this message: "Cocoon 2.2 is a major rewrite: now the old dog is highly modular, Spring-ified, Mavenized, but still more flexible than Struts 2 or Webflow and far more powerful and clean than Wicket or JSF"... but we need better doc for this, I presume. Regards, Luca Morandini www.lucamorandini.it
Re: [vote] Release Cocoon 2.2-final
Luca Morandini wrote:
Reinhard Poetz wrote:
I've prepared the artifacts for the release of Cocoon 2.2 final.
There is much room for improvement in the doc though: don't you think it
should be improved before release ?
What's your plan?
--
Reinhard PötzManaging Director, {Indoqa} GmbH
http://www.indoqa.com/en/people/reinhard.poetz/
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member, PMC Chair[EMAIL PROTECTED]
_
[jira] Commented: (COCOON-2191) XML namespace declaration added in certain circumstances
[ https://issues.apache.org/jira/browse/COCOON-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584774#action_12584774 ] Andreas Hartmann commented on COCOON-2191: -- As a workaround it is sufficient to add an identity XSLT transformation after the i18n transformation. I guess this rids the SAX stream of the prefix mappings. > XML namespace declaration added in certain circumstances > > > Key: COCOON-2191 > URL: https://issues.apache.org/jira/browse/COCOON-2191 > Project: Cocoon > Issue Type: Bug > Components: Blocks: Serializers >Affects Versions: 2.1.12-dev (Current SVN) >Reporter: Andreas Hartmann > > Pipeline: > > > > Source document (test.xml): > > >xmlns:i18n="http://apache.org/cocoon/i18n/2.1";>foo > > > Output of XMLSerializer: > > >foo > http://www.w3.org/XML/1998/namespace"/> > > The xmlns:xml declaration is added due to an underflow of the Namespaces > stack. The field Namespaces.last becomes 1 and therefore the xml namespace is > committed (which I guess should never happen). I'm not sure yet if this is a > problem of the serializers block or maybe of the I18nTransformer. > The problem is that this happens when generating RSS feeds, and IE doesn't > accept them if they contain namespace declarations. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (COCOON-2191) XML namespace declaration added in certain circumstances
XML namespace declaration added in certain circumstances Key: COCOON-2191 URL: https://issues.apache.org/jira/browse/COCOON-2191 Project: Cocoon Issue Type: Bug Components: Blocks: Serializers Affects Versions: 2.1.12-dev (Current SVN) Reporter: Andreas Hartmann Pipeline: Source document (test.xml): http://apache.org/cocoon/i18n/2.1";>foo Output of XMLSerializer: foo http://www.w3.org/XML/1998/namespace"/> The xmlns:xml declaration is added due to an underflow of the Namespaces stack. The field Namespaces.last becomes 1 and therefore the xml namespace is committed (which I guess should never happen). I'm not sure yet if this is a problem of the serializers block or maybe of the I18nTransformer. The problem is that this happens when generating RSS feeds, and IE doesn't accept them if they contain namespace declarations. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [vote] Release Cocoon 2.2-final
Reinhard Poetz wrote: I've prepared the artifacts for the release of Cocoon 2.2 final. There is much room for improvement in the doc though: don't you think it should be improved before release ? Just my 2€c. Regards, Luca Morandini www.lucamorandini.it
[jira] Subscription: COCOON-open-with-patch
Issue Subscription Filter: COCOON-open-with-patch (105 issues) Subscriber: cocoon Key Summary COCOON-2177 ImageOp with requested height & width both zero should be a no-op, instead it throws an exception https://issues.apache.org/jira/browse/COCOON-2177 COCOON-2173 AbstractCachingProcessingPipeline: Two requests can deadlock each other https://issues.apache.org/jira/browse/COCOON-2173 COCOON-2162 [PATCH] Fix for Paginator when accessing out of bounds Pagination page https://issues.apache.org/jira/browse/COCOON-2162 COCOON-2137 XSD Schemas for CForms Development https://issues.apache.org/jira/browse/COCOON-2137 COCOON-2114 fix sorting in TraversableGenerator https://issues.apache.org/jira/browse/COCOON-2114 COCOON-2108 xmodule:flow-attr Does not accept document objects https://issues.apache.org/jira/browse/COCOON-2108 COCOON-2104 [PATCH] Add base URI fixup support to XIncludeTransformer https://issues.apache.org/jira/browse/COCOON-2104 COCOON-2100 Retrieving mimeType returned by pipeline executed from Flow https://issues.apache.org/jira/browse/COCOON-2100 COCOON-2071 Option to turn off pooling for components (probably faster on new JVMs and simpler debugging) https://issues.apache.org/jira/browse/COCOON-2071 COCOON-2063 NekoHTMLTransformer needs to set the default-encoding of the current system to work properly with UTF-8 https://issues.apache.org/jira/browse/COCOON-2063 COCOON-2041 WebDAV Returns improper status on PUT https://issues.apache.org/jira/browse/COCOON-2041 COCOON-2040 Union widget does not work with booleanfield set as case widget https://issues.apache.org/jira/browse/COCOON-2040 COCOON-2037 New DynamicGroup widget https://issues.apache.org/jira/browse/COCOON-2037 COCOON-2035 NPE in the sorter of the EnhancedRepeater https://issues.apache.org/jira/browse/COCOON-2035 COCOON-2032 [PATCH] Sort order in paginated repeater https://issues.apache.org/jira/browse/COCOON-2032 COCOON-2030 submit-on-change doesn't work for a multivaluefield with list-type="checkbox" https://issues.apache.org/jira/browse/COCOON-2030 COCOON-2018 Use thread context class loader to load custom binding classes https://issues.apache.org/jira/browse/COCOON-2018 COCOON-2017 More output beautification options for serializers https://issues.apache.org/jira/browse/COCOON-2017 COCOON-2015 Doctype added twice because root element (html) is inlined https://issues.apache.org/jira/browse/COCOON-2015 COCOON-2002 HTML transformer only works with latin-1 characters https://issues.apache.org/jira/browse/COCOON-2002 COCOON-1985 AbstractCachingProcessingPipeline locking with IncludeTransformer may hang pipeline https://issues.apache.org/jira/browse/COCOON-1985 COCOON-1974 Donating ContextAttributeInputModule https://issues.apache.org/jira/browse/COCOON-1974 COCOON-1973 CaptchaValidator: allow case-insensitive matching https://issues.apache.org/jira/browse/COCOON-1973 COCOON-1964 Redirects inside a block called via the servlet protocol fail https://issues.apache.org/jira/browse/COCOON-1964 COCOON-1963 Add a redirect action to the browser update handler https://issues.apache.org/jira/browse/COCOON-1963 COCOON-1960 Pipeline errors for "generator/reader already set" should provide more information https://issues.apache.org/jira/browse/COCOON-1960 COCOON-1949 [PATCH] load flowscript from file into specified Rhino context object https://issues.apache.org/jira/browse/COCOON-1949 COCOON-1946 [PATCH] - Javaflow Sample errors trying to enhance Javaflow classes and showing cform templates https://issues.apache.org/jira/browse/COCOON-1946 COCOON-1943 [Patch] Parameters in blocks-protocol URIs get decoded too early https://issues.apache.org/jira/browse/COCOON-1943 COCOON-1932 [PATCH] correct styling of disabled suggestion lists https://issues.apache.org/jira/browse/COCOON-1932 COCOON-1929 [PATCH] Reloading classloader in Cocoon 2.2 https://issues.apache.org/jira/browse/COCOON-1929 COCOON-1917 Request Encoding problem: multipart/form vs. url encoded https://issues.apache.org/jira/browse/COCOON-1917 COCOON-1915 Nullable value with additional String or XMLizable in JavaSelectionList https://issues.apache.org/jira/browse/COCOON-1915 COCOON-1914 Text as XMLizable in EmptySelectionList https://issues.apache.org/jira/browse/COCOON-1914 COCOON-1899 [PATCH] Cocoon XML:DB Implementation should not depend on Xindice https://issues.apache.org/jira/browse/COCOON-1899 COCOON-1898 [PATCH] XPatch support for maven-cocoon-deployer-plugin https://issues.apache.org/jira/browse/COCOON-1898 COCOON-1893 XML-Binding: Problem creating
[jira] Closed: (COCOON-2186) Suggest list .. initial value not being displayed
[ https://issues.apache.org/jira/browse/COCOON-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonio Gallardo closed COCOON-2186. Resolution: Fixed Fix Version/s: 2.1.12-dev (Current SVN) > Suggest list .. initial value not being displayed > -- > > Key: COCOON-2186 > URL: https://issues.apache.org/jira/browse/COCOON-2186 > Project: Cocoon > Issue Type: Bug > Components: Blocks: Ajax, Blocks: Forms >Affects Versions: 2.1.11 >Reporter: imran pariyani >Assignee: Antonio Gallardo >Priority: Minor > Fix For: 2.1.12-dev (Current SVN) > > > For the forms field of type suggest with a suggestion list the initial value > is not being displayed ... this dint happen for version 2.1.10 .. but when i > upgraded to version 2.1.11 it no longer sets the initial value .. this bug is > also present for the sample > http://cocoon.zones.apache.org/demos/release/samples/blocks/forms/do-suggest.flow > Initial value of the widget is 16, the widget must show "Bruno Dumon". > > 16 > > after debugging i found out that the widgets value is being set but it isnt > passed on to DOJO as initial value when the DOJO widget is created .. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (COCOON-2186) Suggest list .. initial value not being displayed
[ https://issues.apache.org/jira/browse/COCOON-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonio Gallardo reassigned COCOON-2186: Assignee: Antonio Gallardo > Suggest list .. initial value not being displayed > -- > > Key: COCOON-2186 > URL: https://issues.apache.org/jira/browse/COCOON-2186 > Project: Cocoon > Issue Type: Bug > Components: Blocks: Ajax, Blocks: Forms >Affects Versions: 2.1.11 >Reporter: imran pariyani >Assignee: Antonio Gallardo >Priority: Minor > > For the forms field of type suggest with a suggestion list the initial value > is not being displayed ... this dint happen for version 2.1.10 .. but when i > upgraded to version 2.1.11 it no longer sets the initial value .. this bug is > also present for the sample > http://cocoon.zones.apache.org/demos/release/samples/blocks/forms/do-suggest.flow > Initial value of the widget is 16, the widget must show "Bruno Dumon". > > 16 > > after debugging i found out that the widgets value is being set but it isnt > passed on to DOJO as initial value when the DOJO widget is created .. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [vote] Release Cocoon 2.2-final
Reinhard Poetz wrote:
I've prepared the artifacts for the release of Cocoon 2.2 final. See the
list of
all proposed artifacts below.
+1
--
Reinhard PötzManaging Director, {Indoqa} GmbH
http://www.indoqa.com/en/people/reinhard.poetz/
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member, PMC Chair[EMAIL PROTECTED]
_
[test] Instructions to test Cocoon 2.2-final
The proposed release artifacts of all the modules that we vote on (see the
seperate voting thread) are available at http://people.apache.org/builds/cocoon/
The easiest way to test the artifacts is by adding a "cocoon-staging" profile to
your ~/.m2/settings.xml:
cocoon-staging
cocoon.staging
Cocoon staging repository
http://people.apache.org/builds/cocoon
cocoon.staging
Cocoon staging repository
http://people.apache.org/builds/cocoon
Then change the version number of the artifacts that you use in your POMs
to the number of the proposed artifact and append "-P cocoon-staging" to all
your Maven commands, e.g.
mvn install -P cocoon-staging
- o -
In order to test the archetypes
- cocoon-22-archetype-block-1.0.0
- cocoon-22-archetype-webapp-1.0.0
- cocoon-22-archetype-block-plain-1.0.0
append -DremoteRepositories=http://people.apache.org/builds/cocoon/ to your "mvn
org.apache.maven.plugins:maven-archetype-plugin:1.0-alpha-7:create" commands,
e.g.
mvn org.apache.maven.plugins:maven-archetype-plugin:1.0-alpha-7:create
-DarchetypeGroupId=org.apache.cocoon
-DarchetypeArtifactId=cocoon-22-archetype-block
-DarchetypeVersion=1.0.0
-DgroupId=com.mycompany
-DartifactId=myBlock
-DremoteRepositories=http://people.apache.org/builds/cocoon/
The commands to use the archetypes and explanations of what they are for can be
found at http://cocoon.apache.org/2.2/maven-plugins/ (Note: Make sure that you
set the correct archetypeVersion parameter!).
Note that the -DremoteRepositories switch is broken with the 2.0-alpha versions
of the Maven archetype plugin. Therefore I propose to use 1.0-alpha-7.
- o -
Find the non-Maven release artifacts at
http://people.apache.org/~reinhard/cocoon-staging/. The content is the same as
in the Maven staging repository - the docs come from our site directory in SVN.
- o -
Please test the "getting-started" application
(http://people.apache.org/~reinhard/cocoon-staging/cocoon-getting-started/)
whether it runs at your environment.
- o -
In general, please check if the release artifacts meet all legal
requirements of the ASF. (checksums, signatures, license & notice files)
--
Reinhard PötzManaging Director, {Indoqa} GmbH
http://www.indoqa.com/en/people/reinhard.poetz/
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member, PMC Chair[EMAIL PROTECTED]
_
[vote] Release Cocoon 2.2-final
I've prepared the artifacts for the release of Cocoon 2.2 final. See the list of
all proposed artifacts below.
You can find the staged files for all modules (sources, binaries, javadocs,
checksums, gpg signatures) at
- http://people.apache.org/builds/cocoon/
(Maven 2 repo)
- http://people.apache.org/builds/cocoon/cocoon-2.2-all.tar.gz
(tar archive of all artifacts).
SVN tags of all these artifacts can be found at
http://svn.apache.org/repos/asf/cocoon/tags/cocoon-2.2/.
For the final release I've also created release artifacts for people who don't
want to use Maven 2 or Ivy. These artifacts can be found at -
http://people.apache.org/~reinhard/cocoon-staging/. A tar containing all release
artifacts is available at
http://apache.org/~reinhard/cocoon-2.2-non-maven-all.tar.gz.
Note that there is a special release artifact "cocoon-getting-started" that
creates the structure of a Cocoon project, consisting of a web application and
one block, that can be built by plain Ant only.
Find instructions about how you can test in a seperate mail. Report your
findings to that thread and use this one for voting only. Thanks!
This majority vote stays open for 72 hours.
- o -
SUBPROJECT: COCOON CONFIGURATION
- cocoon-configuration-api-1.0.2.jar
- cocoon-spring-configurator-1.0.2.jar
SUBPROJECT: COCOON SERVLET-SERVICE-FRAMEWORK
- cocoon-servlet-service-impl-1.0.0.jar
- cocoon-servlet-service-components-1.0.0.jar
COCOON CORE
- cocoon-xml-api-1.0.0.jar
- cocoon-xml-impl-1.0.0.jar
- cocoon-xml-resolver-1.0.0.jar
- cocoon-xml-util-1.0.0.jar
- cocoon-thread-api-1.0.0.jar
- cocoon-thread-impl-1.0.0.jar
- cocoon-expression-language-api-1.0.0.jar
- cocoon-expression-language-impl-1.0.0.jar
- cocoon-util-1.0.0.jar
- cocoon-store-impl-1.0.0.jar
- cocoon-pipeline-api-1.0.0.jar
- cocoon-pipeline-impl-1.0.0.jar
- cocoon-pipeline-impl-1.0.0-tests.jar
- cocoon-pipeline-components-1.0.0.jar
- cocoon-sitemap-api-1.0.0.jar
- cocoon-sitemap-impl-1.0.0.jar
- cocoon-sitemap-impl-1.0.0-tests.jar
- cocoon-sitemap-components-1.0.0.jar
- cocoon-core-2.2.0.jar
- cocoon-core-2.2.0-tests.jar
COCOON BLOCKS
- cocoon-template-impl-1.1.0.jar*
- cocoon-flowscript-impl-1.0.0.jar
- cocoon-auth-api-1.0.0.jar
- cocoon-auth-impl-1.0.0.jar
- cocoon-batik-impl-1.0.0.jar
- cocoon-captcha-impl-1.0.0.jar
- cocoon-fop-impl-1.0.0.jar
- cocoon-html-impl-1.0.0.jar
- cocoon-linkrewriter-impl-1.0.0.jar
- cocoon-mail-impl-1.0.0.jar
- cocoon-databases-hsqldb-client-1.0.0.jar
- cocoon-databases-hsqldb-server-1.0.0.jar
- cocoon-databases-mocks-1.0.0.jar
- cocoon-databases-impl-1.0.0.jar
- cocoon-databases-bridge-1.0.0-jar
- cocoon-ajax-impl-1.0.0.jar
- cocoon-apples-impl-1.0.0.jar
- cocoon-forms-impl-1.1.0.jar*
[*] The 1.0.0 releases are still missing but provided for a version that hasn't
been mirgrated to Spring. These artifacts will hopefully follow soon.
COCOON ARCHETYPES
- cocoon-22-archetype-block-1.0.0.jar
- cocoon-22-archetype-block-plain-1.0.0.jar
- cocoon-22-archetype-webapp-1.0.0.jar
COCOON TOOLS
- cocoon-it-fw-1.0.0-M1.jar
- cocoon-maven-plugin-1.0.0-M2.jar
--
Reinhard PötzManaging Director, {Indoqa} GmbH
http://www.indoqa.com/en/people/reinhard.poetz/
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member, PMC Chair[EMAIL PROTECTED]
_
Re: Disabling JavaPrimitiveWrap in flowscript
On Mar 28, 2008, at 1:47 PM, Tobia Conforto wrote: I'd like to disable JavaPrimitiveWrap globally in Cocoon flowscripts. JavaPrimitiveWrap is a Rhino feature that, when disabled, will return strings and numbers from Java calls as native Javascript types, instead of wrapped Java objects. One can disable it on a (flowscript-)thread by thread basis by calling: org .mozilla .javascript .Context .getCurrentContext().getWrapFactory().setJavaPrimitiveWrap(false); but I'd like to disable it globally for all threads, continuations, etc. Any hint will be welcome. In FOM_JavaScriptInterpreter, look for Context.enter() calls. These are the places where you can add your initialization: context.getWrapFactory().setJavaPrimitiveWrap(false); Vadim
[jira] Closed: (COCOON-2188) "mvn install -P allblocks" fails
[
https://issues.apache.org/jira/browse/COCOON-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Kuckartz closed COCOON-2188.
Resolution: Fixed
After
$ mvn install -P allblocks
failed for about a week it suceeded a few minutes ago.
Finally ...
> "mvn install -P allblocks" fails
>
>
> Key: COCOON-2188
> URL: https://issues.apache.org/jira/browse/COCOON-2188
> Project: Cocoon
> Issue Type: Bug
> Components: - Build System: Maven, Blocks: Ajax
>Affects Versions: 2.2-dev (Current SVN)
>Reporter: Andreas Kuckartz
>Priority: Blocker
> Fix For: 2.2-dev (Current SVN)
>
>
> [INFO] Building Cocoon Ajax Block Implementation
> [INFO]task-segment: [install]
> [INFO]
>
> [INFO] [enforcer:enforce-once {execution: enforce-maven}]
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] snapshot
> org.apache.cocoon:cocoon-servlet-service-components:1.0.0-RC2-SNAPSHOT:
> checking for updates from apache.snapshots
> Downloading:
> http://people.apache.org/repo/m2-snapshot-repository/org/apache/cocoon/cocoon-servlet-service-components/1.0.0-RC2-SNAPSHOT/cocoon-servlet-service-components-1.0.0-RC2-SNAPSHOT.pom
> Downloading:
> http://people.apache.org/repo/m2-snapshot-repository/org/apache/cocoon/cocoon-servlet-service-components/1.0.0-RC2-SNAPSHOT/cocoon-servlet-service-components-1.0.0-RC2-SNAPSHOT.jar
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Failed to resolve artifact.
> Missing:
> --
> 1) org.apache.cocoon:cocoon-servlet-service-components:jar:1.0.0-RC2-SNAPSHOT
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.apache.cocoon
> -DartifactId=cocoon-servlet-service-components -Dversion=1.0.0-RC2-SNAPSHOT
> -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.apache.cocoon
> -DartifactId=cocoon-servlet-service-components -Dversion=1.0.0-RC2-SNAPSHOT
> -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) org.apache.cocoon:cocoon-ajax-impl:jar:1.1.0-SNAPSHOT
> 2)
> org.apache.cocoon:cocoon-servlet-service-components:jar:1.0.0-RC2-SNAPSHOT
> --
> 1 required artifact is missing.
> for artifact:
> org.apache.cocoon:cocoon-ajax-impl:jar:1.1.0-SNAPSHOT
> from the specified remote repositories:
> apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),
> central (http://repo1.maven.org/maven2)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Continuum
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all I'm a bit confused about continuum builds. Do we use different continuums? At http://cocoon.zones.apache.org/ we do have a continuum link: http://cocoon.zones.apache.org/continuum/servlet/continuum/ but the nag mails are comming from a continuum at http://vmbuild.apache.org/continuum/ Which is the right one? Thanks Felix -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkfzXucACgkQ2lZVCB08qHEzvgCaAtjEo5HA/hIh+BHMAosXAMke cRAAoNrMzPv1eMcxMN4maih7anbMaTMM =dJph -END PGP SIGNATURE-
Re: [jira] Updated: (COCOON-2188) "mvn install -P allblocks" fails
Hi Grzegorz Kossakowski schrieb: Reinhard Poetz wrote: Argh, any chance to make Continuum find this problems instead of Andreas? Wasn't there some way to delete all org.apache.cocoon:* artifacts from the local Continuum repository as part of integration build? Will need to ask infra folks as Continuum does not offer such feature out-of-box. Definitively, worth investigation. I found some problems about used versions in the parent pom when trying to compile with an local empty m2 repo which I fixed this morning in commits 643794, 643799. I hope this will fix the problem the issue. I'm not sure if I can see at continuum if it works know. If so please close the issue. Regards Felix
Re: [jira] Updated: (COCOON-2188) "mvn install -P allblocks" fails
Reinhard Poetz wrote: > Argh, any chance to make Continuum find this problems instead of > Andreas? Wasn't there some way to delete all org.apache.cocoon:* > artifacts from the local Continuum repository as part of integration > build? Will need to ask infra folks as Continuum does not offer such feature out-of-box. Definitively, worth investigation.. -- Grzegorz Kossakowski
