> > Hi Claus,
> >
> > I am now only getting the following WARNING which will also fail the
> > release buid:
> >
> > ===
> > [WARNING] Javadoc Warnings
> > [WARNING] javadoc: warning - Multiple sources of package comments
> > found f
Hi Gregor
Okay I have a fix now. There is 1 commit on the 3.7.x branch from today.
On Tue, Dec 15, 2020 at 10:31 PM Gregor Zurowski
wrote:
>
> Hi Claus,
>
> I am now only getting the following WARNING which will also fail the
> release buid:
>
> ===
> [WARNING] Jav
On Tue, Dec 15, 2020 at 10:31 PM Gregor Zurowski
wrote:
>
> Hi Claus,
>
> I am now only getting the following WARNING which will also fail the
> release buid:
>
> ===
> [WARNING] Javadoc Warnings
> [WARNING] javadoc: warning - Multiple sources of package c
Hi Claus,
I am now only getting the following WARNING which will also fail the
release buid:
===
[WARNING] Javadoc Warnings
[WARNING] javadoc: warning - Multiple sources of package comments
found for package "javax.annotation"
===
When I build endpoint DSL with `mvn javadoc:javadoc
> > Hi Claus,
> >
> > I've looked into this again and realized that the WARNINGs in the
> > Javadoc creation phase will break the build during release creation. I
> > am still getting a longer list of Javadoc WARNINGs when I run `mvnw
> > javadoc:javadoc` on
Hi Gregor
Ah okay I am working on fixing those WARNs now
On Tue, Dec 15, 2020 at 10:48 AM Gregor Zurowski
wrote:
>
> Hi Claus,
>
> I've looked into this again and realized that the WARNINGs in the
> Javadoc creation phase will break the build during release creation. I
Hi Claus,
I've looked into this again and realized that the WARNINGs in the
Javadoc creation phase will break the build during release creation. I
am still getting a longer list of Javadoc WARNINGs when I run `mvnw
javadoc:javadoc` on `/camel/core/camel-endpointdsl`:
[...]
[WARNING] Ja
Hi Claus,
Thank you so much for your fast response and the fix for this. It is
not an issue for the 3.7.0 release, but mostly for a new build setup I
am working on. As mentioned in my initial post, I am using Java 8
there, but it seems also picky about those Javadoc annotations. I
just checked
Hi Gregor
Okay so the javadoc issue has been fixed. There are about 7 commits on
the 3.7.x branch with CAMEL-15946 as prefix that all together fixes
this.
On Mon, Dec 14, 2020 at 4:00 PM Gregor Zurowski
wrote:
>
> Hi Everyone:
>
> I am getting the following error when building Jav
, 2020 at 4:14 PM Claus Ibsen wrote:
> >
> > Hi
> >
> > I also see this kind of error when building with JDK11. Probably with
> > more sub errors because javadoc is more stricter on JDK11 (eg no
> > @return is a failure, etc.).
> >
> > The endpoint DSL i
>
> I also see this kind of error when building with JDK11. Probably with
> more sub errors because javadoc is more stricter on JDK11 (eg no
> @return is a failure, etc.).
>
> The endpoint DSL is source code generated, and it seems that javadoc
> parser fails such as > should
Hi
I also see this kind of error when building with JDK11. Probably with
more sub errors because javadoc is more stricter on JDK11 (eg no
@return is a failure, etc.).
The endpoint DSL is source code generated, and it seems that javadoc
parser fails such as > should be escaped. That is not rea
Hi Everyone:
I am getting the following error when building Javadoc for DSL Endpoint:
===
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-javadoc-plugin:3.2.0:javadoc
(default-cli) on project camel-endpointdsl: An error has occurred in
Javadoc report generation:
[ERROR] Exit code
lburgazzoli merged pull request #237: Improve the beans and registry
BuildItems' JavaDoc
URL: https://github.com/apache/camel-quarkus/pull/237
This is an automated message from the Apache Git Service.
To respond t
asf-ci commented on issue #237: Improve the beans and registry BuildItems'
JavaDoc
URL: https://github.com/apache/camel-quarkus/pull/237#issuecomment-538978205
Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quark
ppalaga opened a new pull request #237: Improve the beans and registry
BuildItems' JavaDoc
URL: https://github.com/apache/camel-quarkus/pull/237
Followup #230
This is an automated message from the Apache Git Servic
Github user oscerd closed the pull request at:
https://github.com/apache/camel/pull/2502
---
GitHub user tadayosi opened a pull request:
https://github.com/apache/camel/pull/2502
camel-core - Fix typo in XmlConverter javadoc
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tadayosi/camel xmlconverter-typo
Alternatively
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/2398
---
GitHub user gzurowski opened a pull request:
https://github.com/apache/camel/pull/2398
Fix Javadoc linting issues
Some modules use custom Javadoc tags that cause the build to break
when the Javadoc linter checks the sources. This had been disabled
by providing additional
Github user davsclaus closed the pull request at:
https://github.com/apache/camel/pull/2340
---
GitHub user punkhorn opened a pull request:
https://github.com/apache/camel/pull/2340
[CAMEL-11257] Enhance unit tests and fixed Javadoc
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/punkhorn/camel-upstream master
pushed a commit to branch master
> in repository https://gitbox.apache.org/repos/asf/camel.git
>
>
> The following commit(s) were added to refs/heads/master by this push:
> new 0bd8839 RuntimeConfiguration#isAllowUseOriginalMessage: improve
>javadoc
> 0bd8839 is described below
>
owUseOriginalMessage: improve
javadoc
0bd8839 is described below
commit 0bd88399377dbfe0909c002f4e1d364d363e8122
Author: Pascal Schumacher
AuthorDate: Mon Mar 12 20:18:08 2018 +0100
RuntimeConfiguration#isAllowUseOriginalMessage: improve javadoc
---
camel-core/src/main/j
dual-hosted git repository.
pascalschumacher pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/master by this push:
new 0bd8839 RuntimeConfiguration#isAllowUseOriginalMessage: improve javadoc
0bd8839
Github user JSchoreels closed the pull request at:
https://github.com/apache/camel/pull/1654
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user JSchoreels opened a pull request:
https://github.com/apache/camel/pull/1654
Adds javadoc to JDBCAggregationRepository
Hi,
As discussed in the mailing list about "JdbcAggregationRepository doesn't
preserve properties", I've a
Github user johnpoth closed the pull request at:
https://github.com/apache/camel/pull/1465
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is en
GitHub user johnpoth opened a pull request:
https://github.com/apache/camel/pull/1465
CAMEL-10141 Upgrade maven javadoc plugin for java 9 support
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/johnpoth/camel CAMEL-10141
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/1446
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enab
GitHub user PascalSchumacher opened a pull request:
https://github.com/apache/camel/pull/1446
ComponentConfiguration: fix link in javadoc
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/PascalSchumacher/camel
Github user aldettinger closed the pull request at:
https://github.com/apache/camel/pull/1380
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user aldettinger opened a pull request:
https://github.com/apache/camel/pull/1380
CAMEL-10676 : Corrected few javadoc warnings in camel-sql and camel-http
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/aldettinger/camel
Github user aldettinger closed the pull request at:
https://github.com/apache/camel/pull/1262
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user aldettinger opened a pull request:
https://github.com/apache/camel/pull/1262
Fixed some javadoc warnings for camel-core
This PR proposes some javadoc warning fixes. Let me know if a JIRA ticket
is needed before opening a pull request. Would this PR affects too many file
Github user pax95 closed the pull request at:
https://github.com/apache/camel/pull/873
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enable
GitHub user pax95 opened a pull request:
https://github.com/apache/camel/pull/873
CAMEL-9648: Polished javadoc
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/pax95/camel ironmq-javadoc
Alternatively you can review and apply
Github user lburgazzoli closed the pull request at:
https://github.com/apache/camel/pull/842
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user lburgazzoli opened a pull request:
https://github.com/apache/camel/pull/842
CAMEL-9430 - mark braintree javadoc as optional
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/lburgazzoli/apache-camel CAMEL-9430
javadoc, and some don’t. I also noticed
that there seem to be two nightly builds which complete 30-60 minutes apart
each night, where the first build includes the sources and javadoc, but the
second build does not. Here are the available builds, the time they completed,
and whether the sources
Github user kevinearls closed the pull request at:
https://github.com/apache/camel/pull/386
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is e
GitHub user kevinearls opened a pull request:
https://github.com/apache/camel/pull/386
CAMEL-8023 Add javadoc to camel-core endpoints so we have documentation ...
...out of the box
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
Github user wuwen5 closed the pull request at:
https://github.com/apache/camel/pull/309
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
GitHub user wuwen5 opened a pull request:
https://github.com/apache/camel/pull/309
Fix javadoc warning, ChannelPipelineFactory not found
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/wuwen5/camel javadoc-warning
Alternatively
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/227
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
GitHub user ssogabe opened a pull request:
https://github.com/apache/camel/pull/227
[camel-netty] Fixed typo in javadoc
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ssogabe/camel netty
Alternatively you can review and apply
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/215
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
GitHub user ancosen opened a pull request:
https://github.com/apache/camel/pull/215
Camel-7596: Syntax error in javadoc of ExpressionClause.method()
Hi,
This PR is related to: https://issues.apache.org/jira/browse/CAMEL-7596
Bye,
Andrea
You can merge this pull
Hi
Yeah that’s normal, only the major/minor releases are published but not the
patch releases where “current” is a symbolic link to the latest/newest one.
http://camel.apache.org/maven/
Babak
Antoine DESSAIGNE wrote
> Hi everyone,
>
> I've just noticed that the official
Hi everyone,
I've just noticed that the official javadoc [1] is referencing camel 2.13.0
instead of the latest one. Is it normal ?
Thanks,
Antoine.
[1] http://camel.apache.org/maven/current/camel-core/apidocs/index.html
Github user gzurowski closed the pull request at:
https://github.com/apache/camel/pull/70
GitHub user gzurowski opened a pull request:
https://github.com/apache/camel/pull/70
Fix JavaDoc parameters of withProperty method
Fixes the JavaDoc comment of the withProperty() method parameters in
ExchangeBuilder
You can merge this pull request into a Git repository by running
Github user andreaja closed the pull request at:
https://github.com/apache/camel/pull/28
GitHub user andreaja opened a pull request:
https://github.com/apache/camel/pull/28
Improved javadoc for expectedMessageCount.
The javadoc for `expectedMessageCount` really should match up with
setExpectedMessageCount since the side effect of calling `setAssertPeriod` is
so
gt; I will start to review ActiveMQ today and Camel tomorrow. Is someone from
> CXF can take a quick look ?
>
> I will get back to you soon for ActiveMQ and Camel.
>
> Thanks !
> Regards
> JB
>
>
> Original Message
> Subject: [SECURITY] Frame injection vul
JB
Original Message
Subject: [SECURITY] Frame injection vulnerability in published Javadoc
Date: Thu, 20 Jun 2013 09:29:23 +0100
From: Mark Thomas
Reply-To: infrastruct...@apache.org
To: committ...@apache.org
CC: r...@apache.org
Hi All,
Oracle has announced [1], [2] a frame
On Thu, Oct 27, 2011 at 2:43 PM, Hadrian Zbarcea wrote:
> Then we decided that the javadoc for the
> components doesn't make a lot of sense.
Not sure I follow that. Some components' classes have methods over
and above the standard for a base component. MailEndpoint, for
ome too
> time consuming (we also had tests randomly failing mostly due to timing,
> most of them are sorted out now). Then we decided that the javadoc for
> the components doesn't make a lot of sense. So we decided to only put
> out camel-core and camel-spring. Then there was a discussion i
st of them are sorted out now). Then we decided that the javadoc for
the components doesn't make a lot of sense. So we decided to only put
out camel-core and camel-spring. Then there was a discussion iirc about
the need to put the javadoc for the patch releases. As the api shouldn't
I use my IDE and Maven to download the sources/javadocs and read the java
doc in my IDE...
I can live without this sites...
Best,
Christian
Yes, please.
Don
On Thu, Oct 27, 2011 at 12:02 PM, Daniel Kulp wrote:
>
> Claus pointed out to me this morning that the javadoc on the website:
>
> http://camel.apache.org/maven/current/camel-core/apidocs/
>
> is horribly out of date (2.7.0). There aren't really instru
Claus pointed out to me this morning that the javadoc on the website:
http://camel.apache.org/maven/current/camel-core/apidocs/
is horribly out of date (2.7.0).There aren't really instructions on the
website on how they were created and uploaded and such.
The next question is: do we
Yes the html file should be there. Its the package javadoc. It should
briefly tell what the package is, and if possible have a link to the
camel website for more details.
On Mon, May 16, 2011 at 11:43 PM, Fernando Ribeiro
wrote:
> All,
>
> Is
> the
> /camel/components/camel-http
All,
Is
the
/camel/components/camel-http4/src/main/java/org/apache/camel/component/http4/package.html
file really supposed to be there, or can it be deleted?
Thanks,
Fernando
[
https://issues.apache.org/jira/browse/CAMEL-3200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hadrian Zbarcea resolved CAMEL-3200.
Resolution: Fixed
Done.
> Javadoc for Camel
are uploaded to the main site. From 2.3.0
onwards I uploaded all the components javadoc, not just camel-core and
camel-spring. The url format is:
http://camel.apache.org/maven/camel-//apidocs/
http://camel.apache.org/maven/current//apidocs/ points to the
apidocs of the latest release and
[
https://issues.apache.org/jira/browse/CAMEL-3200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hadrian Zbarcea updated CAMEL-3200:
---
Fix Version/s: (was: 2.7.0)
2.8.0
> Javadoc for Camel
s is indeed the way we plan to resolve
this. I also want to go back and add previous javadoc versions down to 2.2.0 at
least (probably not beyond that).
> Javadoc for Camel 2.7
> -
>
> Key: CAMEL-3200
> URL: https://issues.apa
like this:
http://camel.apache.org/maven/camel-2.2.0/camel-core/apidocs/index.html
Could be like this instead:
http://camel.apache.org/maven/camel-latest/camel-core/apidocs/index.html
(or alternatively, have both camel-x.x.x *and* camel-latest)
Similar to what CXF does: http://cxf.apache.org/jav
[
https://issues.apache.org/jira/browse/CAMEL-3200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-3200:
---
Summary: Javadoc for Camel 2.7 (was: Javadoc for Camel 2.6)
> Javadoc for Camel
.
> Workaround the maven javadoc link issue.
>
>
> Key: CAMEL-3679
> URL: https://issues.apache.org/jira/browse/CAMEL-3679
> Project: Camel
> Issue Type: Improvement
>
e maven javadoc link issue.
>
>
> Key: CAMEL-3679
> URL: https://issues.apache.org/jira/browse/CAMEL-3679
> Project: Camel
> Issue Type: Improvement
>Reporter: Willem Jiang
http://jira.codehaus.org/browse/MJAVADOC-286]
of javadoc maven plugin.
We can workaround it by setting the detectOfflineLinks option to be false.
> Workaround the maven javadoc link issue.
>
>
> Key: CAMEL-3679
>
Workaround the maven javadoc link issue.
Key: CAMEL-3679
URL: https://issues.apache.org/jira/browse/CAMEL-3679
Project: Camel
Issue Type: Improvement
Reporter: Willem Jiang
o be able to release 2.6.0.
> Javadoc for Camel 2.6
> -
>
> Key: CAMEL-3200
> URL: https://issues.apache.org/jira/browse/CAMEL-3200
> Project: Camel
> Issue Type: Task
> Components: website
[
https://issues.apache.org/jira/browse/CAMEL-3200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hadrian Zbarcea updated CAMEL-3200:
---
Fix Version/s: (was: 2.6.0)
2.7.0
> Javadoc for Camel
[
https://issues.apache.org/jira/browse/CAMEL-3200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-3200:
---
Summary: Javadoc for Camel 2.6 (was: Javadoc for Camel 2.4 )
> Javadoc for Camel
[
https://issues.apache.org/activemq/browse/CAMEL-3200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-3200:
---
Fix Version/s: (was: 2.5.0)
2.6.0
> Javadoc for Camel
t as much that it's manual as being very
time consuming. This is done during the mvn site goal and a lot of reports are
generated, not just javadoc. I am also trying to automate and parallelize the
release process, hopefully in time for 3.0.
> Javadoc f
but the javadoc is not updated on every release as its a manual process
and takes time.
Hadrian will update it for the 2.5 release.
> Javadoc for Camel 2.4
> --
>
> Key: CAMEL-3200
> URL: https://issues.apache.org/activemq/br
Javadoc for Camel 2.4
--
Key: CAMEL-3200
URL: https://issues.apache.org/activemq/browse/CAMEL-3200
Project: Apache Camel
Issue Type: Bug
Components: website
Affects Versions: 2.4.0
Reporter
ate Exchange javadoc to better explain properties, in, out, mep etc.
> ---
>
> Key: CAMEL-3157
> URL: https://issues.apache.org/activemq/browse/CAMEL-3157
> Project: Apache Came
be a comment that the getOut/getIn methods does
not map to the InOut/InOnly patterns.
> Update Exchange javadoc to better explain properties, in, out, mep etc.
> ---
>
> Key: CAMEL-3157
>
ttps://svn.apache.org/repos/asf/camel/trunk/camel-core/src/main/java/org/apache/camel/Exchange.java
Feedback welcome
> Update Exchange javadoc to better explain properties, in, out, mep etc.
> ---
>
>
Update Exchange javadoc to better explain properties, in, out, mep etc.
---
Key: CAMEL-3157
URL: https://issues.apache.org/activemq/browse/CAMEL-3157
Project: Apache Camel
[
https://issues.apache.org/activemq/browse/CAMEL-1394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59370#action_59370
]
Claus Ibsen commented on CAMEL-1394:
Seeing the javadoc for the converters does
e Static / Instance methods for type converters in the
> web console so that they render nicely and have hypertext links to the
> javad
have now updated the javadoc to 2.2.0 release.
> nightly CI build doesn't deploy the website - the online javadoc is ancient
> ---
>
> Key: CAMEL-1619
> URL: https://issues
JAXB now. But that ticket was
target for JAXB 2.1.13 which is the next release. So may SUN get it into the
JAXB eventually.
> hack the XSD generator (patching JAXB's mvn plugin) so that the javadoc is
> included in the generated XSD a
patching JAXB's mvn plugin) so that the javadoc is
> included in the generated XSD as documentation
> -
>
> Key: CAMEL-632
> UR
API javadoc which is actually
based on Camel 2.2 release
http://fusesource.com/docs/router/2.2/apidoc/index.html
> nightly CI build doesn't deploy the website - the online javadoc is ancient
> ---
>
>
> Website Links to JavaDoc broken.
>
>
> Key: CAMEL-2681
> URL: https://issues.apache.org/activemq/browse/CAMEL-2681
> Project: Apache Camel
> Issue Type: Improvement
> Components: websi
1 PM:
---
indexValidator.txt is http://validator.w3.org/checklink results for index page,
with redundant comments deleted to save upload space.
javadocValidator.txt, same for Javadoc page.
was (Author: thesamim):
First file is http://validator.w3.org/checklink results for index page,
://validator.w3.org/checklink results for index page, with
redundant comments deleted to save upload space.
Second file, same for Javadoc page.
> Website Links to JavaDoc broken.
>
>
> Key: CAMEL-2681
> URL: https://is
Website Links to JavaDoc broken.
Key: CAMEL-2681
URL: https://issues.apache.org/activemq/browse/CAMEL-2681
Project: Apache Camel
Issue Type: Improvement
Components: website
Environment
ploy the website - the online javadoc is ancient
> ---
>
> Key: CAMEL-1619
> URL: https://issues.apache.org/activemq/browse/CAMEL-1619
> Project: Apache Camel
>
ets online
>
> Claus Ibsen-2 wrote:
>>
>> Hi
>>
>> I think one of them is for regular javadoc if you run mvn javadoc:javadoc
>> Where as the other is for release.
>>
>>
>> On Wed, Dec 2, 2009 at 9:04 AM, Claus Ibsen wrote:
>>> On Tue, Dec
Hi,
Hmmm the second came in with revision 880905 (~ 3 weeks ago) as a fix to
remove maven 3 warnings ... maybe we should contact janstey for the reason
of the second.
Claus Ibsen-2 wrote:
>
> Hi
>
> I think one of them is for regular javadoc if you run mvn javadoc:javadoc
&g
Hi
I think one of them is for regular javadoc if you run mvn javadoc:javadoc
Where as the other is for release.
On Wed, Dec 2, 2009 at 9:04 AM, Claus Ibsen wrote:
> On Tue, Dec 1, 2009 at 3:19 PM, akuhtz wrote:
>>
>> Hi,
>>
>> I've seen that the maven
On Tue, Dec 1, 2009 at 3:19 PM, akuhtz wrote:
>
> Hi,
>
> I've seen that the maven-javadoc-plugin defined twice in pluginManagement
> section of pom.xml. Is this a mistake or intended? (see line 155+ for the
> first and line 347+ for the second).
>
Could vert well be a
1 - 100 of 122 matches
Mail list logo
